Wireless communication accessory for a mobile device

ABSTRACT

A wireless communication accessory for a mobile communication device comprising: a casing that conforms, at least partially, to the outer shape of the mobile communication device; a processing circuit housed within the casing and configured to process a first data; and a wireless transmitter coupled to the processing circuit, where the transmitter is configured to transmit the first data. The wireless communication accessory may further comprise a wireless receiver that is configured to receive a second data from an external wireless device. The first data may be associated with any or all of the following: payment card information for processing purchase transactions; public transportation account information for processing travel credits on public transportation systems; and access card information for gaining access into restricted areas.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.13/492,785, titled WIRELESS COMMUNICATION ACCESSORY FOR A MOBILE DEVICE,filed Jun. 8, 2012 and now issued as U.S. Pat. No. 9,123,935, which is acontinuation-in-part to U.S. patent application Ser. No. 12/357,262,titled BATTERY PACK, HOLSTER, AND EXTENDIBLE PROCESSING AND INTERFACEPLATFORM FOR MOBILE DEVICES, filed Jan. 21, 2009 and now issued as U.S.Pat. No. 8,367,235, which in turn claims the benefit of U.S. ProvisionalPatent Application No. 61/021,897, titled BATTERY PACK AND HOLSTER FORMOBILE DEVICES, and filed Jan. 18, 2008. U.S. patent application Ser.No. 13/492,785 additionally claims the benefit of U.S. ProvisionalPatent Application No. 61/495,848, titled NEAR FIELD COMMUNICATIONACCESSORY FOR A MOBILE DEVICE, filed Jun. 10, 2011. Each of theabove-identified applications is incorporated by reference herein in itsentirety.

FIELD OF THE DISCLOSURE

Aspects relate to accessories for mobile devices and, more particularly,to an external protective case and/or holster for mobile electronicdevices, where the external protective case/holster incorporates abattery pack, an external processing accessory, a payment processingaccessory, television signal receiver accessory, a wirelesscommunication accessory, a near field communication accessory, and/or amodular multi-input/output device.

BACKGROUND

Many mobile devices (e.g., mobile phones, digital assistants, mobilecommunication devices, handheld computing devices, personalmusic/video/content players and storage devices) are often powered bybattery power sources. Such battery power sources are often housedwithin the mobile device and may be changed and/or recharged as needed.However, as more powerful mobile devices are designed, these tend toconsume power more quickly, thereby shortening the time between charges.This tends to limit the usefulness of the mobile device since the usermust find a power source to recharge the battery source and wait untilit is recharged.

Additionally, such mobile devices are designed to satisfy the needs of awide array of consumers. For instance, such mobile devices may havesomewhat limited processing capabilities (e.g., to extend battery power)and limited input/output capabilities. Consequently, users who wish toextend the capabilities of the mobile device to implement various typesof solutions are prevented from doing so.

SUMMARY

In one embodiment, a wireless communication accessory for a mobilecommunication device is disclosed, comprising: a casing that conforms,at least partially, to the outer shape of the mobile communicationdevice; a processing circuit housed within the casing and configured toprocess a first data; and a wireless transmitter coupled to theprocessing circuit, where the transmitter is configured to transmit thefirst data. In another embodiment, the wireless communication accessoryfurther comprises a wireless receiver coupled to the processing circuit,where the receiver is configured to receive a second data. In anotherembodiment, the wireless accessory further comprises an internalinterface coupled to a mobile device interface of the mobilecommunication device to allow for communication between the mobilecommunication device and the wireless communication accessory.

In another embodiment, the casing defines a cavity that removablysecures the mobile communication device, and wherein at least onesurface of the mobile communication device remains exposed. In anotherembodiment, the first data is associated with payment card information,and the first data is transmitted by the wireless communicationtransmitter to execute a purchase transaction. In another embodiment,the first data is associated with a public transportation account, andthe first data is transmitted by the wireless communication transmitterto purchase transportation. In another embodiment, the first data isassociated with access card information, and the first data istransmitted by the wireless communication transmitter to allow access toa restricted area. In another embodiment, the second data is coupon dataassociated with a merchant. In another embodiment, the wirelesscommunication accessory further comprises a cryptography moduleconfigured to encrypt the first data prior to transmission by thewireless communication transmitter.

In another embodiment, the wireless communication accessory furthercomprises an application that when executed by the processing circuitcauses the wireless communication accessory to log a time, date, andlocation associated with the purchase transaction. In anotherembodiment, the mobile communication device prompts the user to enter apassword or personal identification number (PIN) prior to execution ofthe purchase transaction by the wireless communication accessory. Inanother embodiment, a GPS unit is used to determine the location of thepurchase transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a perspective view of a battery pack for a mobiledevice according to one example.

FIG. 2 illustrates how a mobile device can be housed within the batterypack of FIG. 1.

FIG. 3 illustrates a front view of the battery pack of FIG. 1.

FIG. 4 illustrates the battery pack of FIG. 1 in an open configuration.

FIG. 5 illustrates a top view of the battery pack of FIG. 1.

FIG. 6 illustrates a bottom view of the battery pack of FIG. 1.

FIG. 7 illustrates a back view of the battery pack of FIG. 1.

FIG. 8 illustrates back view of the battery pack of FIG. 1 in an openposition.

FIG. 9 illustrates a first side view of the battery pack of FIG. 1.

FIG. 10 illustrates the first side view of the battery pack of FIG. 1 inan open position.

FIG. 11 illustrates a second side view of the battery pack of FIG. 1.

FIG. 12 illustrates the second side view of the battery pack of FIG. 1in an open position.

FIG. 13 is an exploded view of components of the battery pack of FIG. 1.

FIG. 14 illustrates a block diagram for the battery pack of FIG. 1.

FIG. 15 illustrates a perspective view of the battery pack.

FIG. 16 illustrates a perspective view of the battery pack with a mobiledevice 1602 inserted therein.

FIG. 17 illustrates a battery pack that also operates as an extendibleprocessing and/or interfacing platform for a mobile device

FIG. 18 illustrates another perspective view of the battery pack.

FIG. 19 illustrates a front view of the battery pack.

FIG. 20 illustrates a front view of the battery pack 1502 with themobile device inserted therein.

FIG. 21 illustrates a back view of the battery pack with the mobiledevice inserted therein.

FIG. 22 illustrates a side view of the battery pack with and without themobile device.

FIGS. 23A and 23B illustrate a functional block diagram of oneembodiment of the components of the mobile device, the externalprocessing accessory, and the application specific accessory.

FIG. 24 illustrates a functional block diagram of one embodiment of apayment processing mobile accessory adapted to read data stored onmagnetic strips of a payment card.

FIG. 25 illustrates a front perspective view of the payment processingaccessory.

FIG. 26 illustrates a front view of the payment processing accessory.

FIGS. 27A and 27B illustrate perspective views of a mobile device housedwithin the casing of the payment processing accessory.

FIG. 28 illustrates a bottom view of the payment processing accessory.

FIG. 29 illustrates a side view of the payment processing accessory.

FIG. 30 illustrates the top section of the payment processing accessorydetached from the bottom section.

FIG. 31 illustrates an exploded view of the bottom section of e paymentprocessing accessory.

FIG. 32A-32C illustrate perspective views of the internal contents ofthe bottom section of the payment processing accessory.

FIG. 33 illustrates a functional block diagram of one embodiment of apayment processing mobile accessory adapted to read data stored on achip embedded into a payment card.

FIG. 34 illustrates a functional block diagram of a near fieldcommunication mobile accessory.

FIG. 35 illustrates a functional block diagram of a television signalreceiver and battery pack mobile accessory.

FIG. 36 illustrates a perspective view of a two piece casing that may beused to house an external processing accessory, NFC accessory, TVreceiver accessory, or a payment processing accessory.

FIG. 37 illustrates the casing of FIG. 36 with a mobile device housedtherein.

FIG. 38 illustrates a front view of the casing of FIG. 36 in a closedconfiguration.

FIG. 39 illustrates a front view of the casing of FIG. 36 in an openconfiguration.

FIG. 40 illustrates a top view of the casing of FIG. 36.

FIG. 41 illustrates a bottom view of the casing of FIG. 36.

FIG. 42 illustrates a back view of the casing of FIG. 36.

FIG. 43 illustrates a perspective view of a single piece casing thatleaves at least one surface of the mobile device exposed. The casing maybe used to house an external processing accessory, NFC accessory, TVreceiver accessory, or a payment processing accessory.

FIG. 44 illustrates the casing of FIG. 43 with a mobile device housedtherein.

FIG. 45 illustrates a perspective view of a single piece casing thatattaches onto the end of the mobile device. The casing may be used tohouse an external processing accessory, NFC accessory, TV receiveraccessory, or a payment processing accessory.

FIG. 46 illustrates a perspective view of a single piece casing attachedonto the end of the mobile device.

FIG. 47 illustrates a functional block diagram of a two-piece modularmobile device accessory scheme that comprises a bottom module and topmodule.

FIG. 48 illustrates a functional block diagram of a three-piece modularmobile device accessory scheme that comprises a bottom module, middlemodule, and top module.

FIG. 49 illustrates a functional block diagram of a data managementsystem that allows a mobile device equipped with a data managementmobile accessory to synchronize with and update data stored on a server.

FIG. 50 illustrates a functional block diagram of one embodiment of thedata management mobile accessory.

FIG. 51 illustrates a functional block diagram of one embodiment of anexternal processing mobile accessory configured to provide additionalhardware and/or software resources to an application specific mobiledevice accessory and a mobile device.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the invention.However, the invention may be practiced without these specific details.In other instances, well known methods, procedures, and/or componentshave not been described in detail so as not to unnecessarily obscureaspects of the invention.

Various embodiments provide battery packs shaped to conform to theexternal shape of a mobile device, thereby providing a permanent orlong-term replacement power source without significantly affecting thesize and usability of the mobile device.

According to one feature, the wireless communication module could be anearfield communication (NFC) interface. In this way, even non-NFCenabled mobile device could participate in NFC transactions. For thepurpose of illustration, many of the figures and specific examplesdescribe NFC modules; however, the invention includes not only NFCinterfaces or even radio frequency interfaces generally, but is intendedto cover all wireless communication types. Among the expressly includedwireless communication methods are radio, NFC, Bluetooth, Wi-Fi,cellular, infrared, satellite, GPD, electromagnetic radiation, IEEE802.15.4, wireless USB, UWB, 6LoWPAN, HSPA+, LTE, GSM, WiMAX, and EV-DO.The technology is not limited to only these communication standards, butat least all of these standards are expressly included within themeaning of a wireless communication.

According to another feature, the battery pack may provide rechargepower to the mobile device while also providing an external signalingand/or charging interface to the mobile device. This way, the mobiledevice need not be removed from the battery pack in order to charge itor provide data (e.g., synchronization, etc.).

According to yet another feature, the battery pack may include one ormore different types of communication interfaces to extend thecommunication capabilities of the mobile device. This allows the mobiledevice to communicate via other interfaces that may not be built intothe mobile device.

According to yet another feature, the battery pack may include one ormore processors to extend the processing capabilities of the batterypack. For instance, the one or more processors may increase theprocessing capabilities of the battery pack and/or providepurpose-specific processors. That is, the interface between the batterypack and mobile device may allow the mobile device to use the one ormore processors to execute application on the battery pack. Note thatsuch applications may, in some instances, continue to operate even ifthe mobile device is detached from the battery pack.

According to yet another feature, the battery pack may include andinductive recharging device or a near-distance recharging device no thatits power cells may be recharged without actually physically plugging itto a recharge power source.

First Embodiment of Battery Pack

FIG. 1 illustrates a perspective view of a battery pack for a mobiledevice according to one example. In this example, the battery pack 100is shaped to receive or house a mobile phone within a contoured cavity102. The battery pack 100 has an integrated rechargeable power cellcapable of providing power to operate and/or recharge a mobile devicemobile device. For illustrative purposes, mobile device is depicted asthe mobile communication device sold under the trademark iPhone by AppleInc.; it is understood by those familiar with the art that other mobiledevices such as computers, mobile phones, media players, music players,personal digital assistants (PDAs), tablet computers, and the like maybe equally applicable.

FIG. 2 illustrates how a mobile device can be housed within the batterypack 100 of FIG. 1. As can be appreciated from this figure, the batterypack 100 is shaped to closely wrap around the mobile device 202 andserves as a protective case for the mobile device 202.

FIG. 3 illustrates a front view of the battery pack 100 of FIG. 1. Thebattery pack 100 includes a back plane 304, first and second sides 306and 308, a bottom side 312, and a top side 314. The back plane 304,first and second sides 306, bottom side 312 and top side 314 may beshaped to form a pocket or cavity 102 in which a mobile device to bepowered can be housed. The top side 314 of the battery pack 100 mayslide out to allow insertion and removal of the mobile device.

Referring again to FIG. 1, the battery pack 100 may include one or moreopenings 104, 108, 110, and 112 to facilitate access to various featuresof the mobile phone. For instance, a first opening 104 on the back plane304 of the battery pack 100 may allow unobstructed view for a cameralens on the back of the mobile device. A second opening 108 may provideaccess to a screen on/off switch for the mobile device. A third opening110 may provide access to an audio jack on the mobile device. A fourthopening 112 on the first side 306 may provide access to a volume controlsliding switch.

The battery pack 100 may also include a connector or interface 106within the cavity 102 (e.g., on the bottom side 312) through which powercan be provided to the mobile device from the internal power cell of thebattery pack 100. Additionally, the connector 106 may be coupled to anexternal interface to provide input and/or output signals to the mobiledevice.

From FIG. 1, it can be appreciated that the battery pack may include twosections that separate to allow insertion of the mobile device and canthen be coupled together to secure the mobile device in place. The sizeand shape of the battery pack 100 may be approximately that of theexternal contour of a mobile device to which it is intended to providepower.

FIG. 4 illustrates the battery pack of FIG. 1 in an open configuration.The battery pack 100 may include a bottom section 402 and a top section404 that can be separated from each other to insert a mobile devicewithin the battery pack 100 and can then be coupled together secure themobile device in place. For example, the bottom section 402 may includereceiving grooves 406 a and 406 b that receive rails 408 a and 408 bfrom the top section 404. In this manner, the top section 404 can becoupled to the bottom section 402 by pressure fit. For example, a tonguesection 802 (FIG. 8) may slide on to the top section 404 such that anengaging tab 412 couples into a receiving groove 804 (FIG. 8) to securethe top section 404 to the bottom section 402.

FIG. 5 illustrates a top view of the battery pack 100 of FIG. 1. In thisview, the top side 314 of the battery pack 100 is shown and the firstopening 104, second opening 108, and third opening 110 can beappreciated.

FIG. 6 illustrates a bottom view of the battery pack 100 of FIG. 1. Inthis view, the bottom side 312 of the battery pack 100 is shown. In thisview, an external interface 602 (e.g., mini or micro USB connector) isshown. This external interface 602 may serve to recharge the internalpower cell of the battery pack. Additionally, the external interface 602may also provide a pass-through signaling interface for the internalconnector or interface 106, thereby allowing the mobile device tocommunicate via the external interface 602. A switch 604 may also belocated on the bottom side 312 of the battery pack and can function toswitch power from the battery pack On or Off. That is, when the mobiledevice has sufficient power on its own, the power cell of the batterypack is not needed and can be switched Off until it is needed.

FIG. 7 illustrates a back view of the battery pack 100 of FIG. 1. Inthis example, a test button 702 is provided that, when pushed, causesplurality of LED lights 704 to indicate the power or charge level of theinternal power cell of the battery pack 100.

FIG. 8 illustrates back view of the battery pack 100 of FIG. 1 in anopen position.

FIG. 9 illustrates a first side view of the battery pack of FIG. 1.

FIG. 10 illustrates the first side view of the battery pack of FIG. 1 inan open position.

FIG. 11 illustrates a second side view of the battery pack of FIG. 1.

FIG. 12 illustrates the second side view of the battery pack of FIG. 1in an open position.

FIG. 13 is an exploded view of components of the battery pack of FIG. 1.In this example, the battery pack may include a first bottom section1302 and a second bottom section 1304 which form a top and bottom shellin between which one or more circuit boards 1308, 1310, and/or 1312and/or one or more power cells 1306 are housed. That is, the circuitsboards 1308, 1310, 1312 and/or power cents) 1306 are sandwiched betweenthe top and bottom sections 1302 and 1304 of the battery pack 100.Consequently, the rechargeable power cell(s) 1306 may be housed withinthe thickness of the back plane of the battery pack.

In some instance, the circuit boards and or power cell of the batterypack may cause interference with the antenna or signaling of the mobiledevice which is in close proximity. Consequently, one aspect providesfor reducing the size of a primary circuit board 1308 by addingsecondary circuit boards 1310 and 1312 which are electrically coupled tothe primary circuit board 1308. This allows reducing the size of thecircuit board 1308 thereby reducing interference to the antenna of themobile device. Additionally, the ground for the power cell 1306 may becoupled to the ground for the mobile device (via the internal interface106) to reduce interference to the mobile device.

FIG. 14 illustrates a block diagram for the battery pack 100 of FIG. 1.The battery pack 1402 may include a power cell 1404, an internalinterface 1406, an external interface 1408, and charge level indicator1410. The internal interface 1406 may be adapted to provide a mobiledevice power from the power cell 1404 as well as passing signal to/fromthe mobile device to the external interface 1408. The external interface1408 may allow recharging of the power cell 1404 as well as passingsignals to/from the mobile device via the internal interface 1406. Aswitch 1412 may allow switching power from the power cell 1404 to themobile device On and Off as desired. Also, a charge level indicator 1410permits displaying of the charge level of the power cell 1404.Additionally, a recharging module 1412 serves to recharge to power cell1404 when needed.

Second Embodiment of Battery Pack

FIGS. 15-16 and 18-22 illustrate yet another embodiment of the powerpack. In this embodiment, the power pack may operate as previouslydisclosed but does not include a top section. By removing the topsection, the battery pack is more compact in size and ergonomic so thatit does not significantly increase or change the size, thickness, and/orshape of mobile communication device 1602 secured thereto.

FIG. 15 illustrates a perspective view of the battery pack 1502.

FIG. 16 illustrates a perspective view of the battery pack 1502 with amobile device 1602 inserted therein.

FIG. 18 illustrates another perspective view of the battery pack 1502.

FIG. 19 illustrates a front view of the battery pack 1502.

FIG. 20 illustrates a front view of the battery pack 1502 with themobile device inserted therein.

FIG. 21 illustrates a back view of the battery pack 1502 with the mobiledevice 1602 inserted therein.

FIG. 22 illustrates a side view of the battery pack 1502 with andwithout the mobile device 1602. Note that, in some embodiments, the leftand right sides may be symmetrical.

Extendible Processing and Interfacing Platform

FIG. 17 illustrates a battery pack that also operates as an extendibleprocessing and/or interfacing platform for a mobile device. In oneexample, the battery pack 1702 may operate as described with referenceto FIG. 14. In addition, the battery pack may also include one or moreprocessors 1706 and/or one or more interfaces 1708. The one or moreprocessors 1706 a and 1706 b may allow a mobile device coupled to theinternal interface 1406 to extend its processing capabilities. Forinstance, the mobile device may cause one or more applications to beexecuted on the one or more processors 1706 while using a user displayon the mobile device as an output interface. Additionally, theprocessors 1706 a and/or 1706 b may be purpose-specific processors thatallow the mobile device to perform particular tasks not otherwisepossible on its own. For example, the processors 1706 may provideanalog-to-digital conversion, audio signal sampling, temperaturemeasuring, etc., which may not be available to the standard mobiledevice.

The one or more interfaces 1708 a and 1708 b may also provide the mobiledevice a method by which to communicate or acquire signals. Theseinterfaces 1708 may effectively expand the communication interfacesavailable to the mobile device by providing wired and/or wirelesscommunication interfaces for various types of signals (e,g., audio,infrared, etc.).

The battery pack 1702 may also include a recharging module 1704 thatfacilitates recharging of the power cell 1404. For example, therecharging module 1704 may be a wireless or cordless charging devicethat inductively or otherwise facilitates recharging of the power cell1404.

In one example implementation, the battery pack 1702 may be adapted tofunction as a Medical Processing Unit which may have build-incapabilities for monitoring real-time health conditions (e.g., alcohollevels in breath, pulse, temperature, blood pressure, test and/ordiagnose diabetes, etc.) via build-in test port. Consequently, thebattery pack 1702 can collect and/or process such collected data andstore it in the mobile device. Note that the processing of such data maybe directed by an application that operates either on the one or moreprocessors of the battery pack 1702 and/or the processor(s) of themobile device. According to one feature, if an abnormal health conditionoccurs (e.g., a heart attack, fainting, seizure, etc.), the MedicalProcessing Unit may detect this condition and automatically activate themobile device (e.g., cellular phone) to send urgent text message oremails to a doctor, hospital, or emergency responder. The respondingparty (doctor, hospital, emergency responder) may be able to locate thepatient via a global positioning system or information from the mobiledevice.

In another example implementation, the battery pack 1702 may be adaptedto function as a Gaming Processing Unit that may include the capabilityof turning the mobile device into a real handheld gaming device withjoysticks or large PSP/DS type of gaming buttons and communicationdevices. Consequently, the mobile device may be configured to operate asan input and/or output interface (e.g., via a display on the mobiledevice or battery pack) for a game.

In yet another example, the battery pack 1702 may be adapted to functionas a Home Entertainment Unit that may include the capability of turningthe mobile device into a Universal Smart Remote Control which cancontrol all the IR activated units in a home or office (e.g., controlgarage doors, television sets, security alarm, air conditioning, etc.).For this purpose, the battery pack 1702 may include various interfaces1708 that provide the specific infrared and/or wireless protocols and/orsignaling to control such devices.

External Processing Mobile Accessory

As discussed above, in reference to FIG. 17, the battery pack 1702 mayoperate as an extendible processing unit that comprises one or moreprocessors 1706 a and 1706 b, and one or more interfaces 1708 a and 1708b. The one or more processors 1706 a and 1706 b may allow a mobiledevice coupled to the internal interface 1406 to extend its processingcapabilities, while the one or more interfaces 1708 a and 1708 b mayalso provide the mobile device a method by which to communicate oracquire signals. This concept may be extended to an external processingmobile accessory that may include one or more processors and/or devices(with or without the external battery) that extends the functionalityof, or adds capabilities to the mobile device.

More particularly, the external processing accessory may serve as aprocessing platform to which other application specific accessories mayinterchangeably couple to, in order to take advantage of the externalprocessing accessory's hardware (e.g., processing circuitry, memory, I/Ointerfaces, etc.), and/or software (e.g., firmware, applications,operating system, etc.). For example, a third party vendor may wish tomanufacture an application specific mobile device accessory thatmeasures blood glucose levels. Ordinarily, the manufacturer of the bloodglucose measuring accessory would have to design and manufacture theaccessory to have complex hardware components and associatedsoftware/firmware that serve to measure, analyze, and communicate theblood glucose level information collected to the mobile device. Forexample, the accessory may have to comprise, at least, one or moreprocessors, memory, and an interface that communicates with the mobiledevice. However, these hardware components used within a blood glucosemeasuring apparatus are all used to perform only one function: reportinga user's blood glucose levels. The blood glucose measuring apparatuswould also necessarily require other hardware too, such as, an inputthat receives blood from the user.

If the third party vendor now wished to manufacture another applicationspecific mobile device accessory, such as a bar code reader, anotheraccessory would have to be designed and manufactured having processors,memory, and a mobile device communications interface, all dedicated—thistime—to reading barcodes. Duplication of such hardware resources toperform different tasks is not cost effective. Therefore, there is aneed for an external processing accessory that may be removably coupledto a plurality of different application specific accessories, so thatthe application specific accessories may share the external processingaccessory's processors, memory, and communications interfaces to handlecommon tasks such as processing, storing data, and/or communicating withthe mobile device. This would reduce the design complexity and cost ofthe application specific accessories.

FIG. 51 illustrates a functional block diagram of one embodiment of anexternal processing mobile accessory 2302 configured to provideadditional hardware and/or software (e.g., firmware, applications,operating system, etc.) resources to an application specific mobiledevice accessory 2380 and a mobile device 2350. The external processingaccessory 2302 may be housed within a casing that removably couples tothe mobile device 2350. The internal interface 2310 of the externalprocessing accessory 2302 transmits data to and receives data from themobile device interface 2360 of the mobile device 2350. The externalprocessing accessory 2302 also removably couples to the applicationspecific accessory 2380. The external interface 2312 of the externalprocessing accessory 2302 transmits data to and receives data from thecommunication interface 2390 of the application specific accessory 2380.

The external processing accessory 2302 serves as abridge between theapplication specific accessory 2380 and the mobile device 2350. Theexternal processing accessory 2302 may provide for a bulk of theprocessing, storing, and mobile device interface communication needs ofthe application specific device 2380. Thus, the application specificdevice 2380 may only need to comprise those hardware components that areuniquely necessary to perform its task (e.g., a barcode scanner inputdevice for a barcode reader accessory; a blood reception unit for ablood glucose measuring accessory, etc.). Various application specificdevices 2380 may be interchangeably coupled to the external processingaccessory 2302 for use with the mobile device 2350. The variousapplication specific devices 2380 may be manufactured by different thirdparty entities.

The application specific accessory 2380 may be, for example, a bloodglucose measuring accessory, a blood or breath alcohol measuringaccessory, a finger print image reader accessory, a retinal image readeraccessory, a barcode reader accessory, a matrix code (i.e., 2D barcode)reader accessory, a near field communication device accessory, amagnetic strip payment card reader accessory, a smart card (contactlessand contact) payment card reader, or an inventory management accessory.The application specific accessory 2380 is not limited to theseembodiments, but rather, it may be any accessory device with a specificapplication.

FIGS. 23A and 23B illustrate a functional block diagram of oneembodiment of the components of the mobile device 2350, the externalprocessing accessory 2302, and the application specific accessory 2380.The external processing accessory 2302 may comprise a memory circuit2304 (also referred to as memory circuits), one or more processors 2306a and 2306 b (also referred to as processing circuits), one or moreinput and output (I/O) interfaces 2308 a and 2308 b, an internalinterface 2310, an external interface 2312, a cryptography module 2314,a power cell module 2316 (e.g., battery power source), an integrateddisplay 2318, a bus 2320, and/or a power bus 2322. The bus 2320 servesas a communication interface between the one or more processors 2306 aand 2306 b, the one or more I/O interfaces 2308 a and 2308 b, the memorycircuit 2304, the internal interface 2310, the external interface 2312,the cryptography module 2314, the power cell module 2316, and/orintegrated display 2318.

The external processing accessory 2302 may transmit and receive data tothe mobile device 2350. Specifically, the internal interface 2310 of theexternal processing accessory 2302 communicatively couples to the mobiledevice interface 2360 of the mobile device 2350. In one embodiment, theinternal interface 2310 and mobile device interface 2360 physicallycouple to one another to transmit data through a wire, bus, and/orelectrical contact connection. Such a connection may also serve tophysically secure the external processing device 2302 to the mobiledevice 2350. Alternatively, or in addition to such a wired connection,the internal interface 2310 may transmit and receive data to the mobiledevice 2350 wirelessly, using for example a Bluetooth standard, or anyone of the 802.11 standards.

Moreover, the external processing accessory 2302 may transmit to andreceive data from the application specific accessory 2380. Specifically,the external interface 2312 of the external processing accessory 2302communicatively couples to the communication interface 2390 of theapplication specific accessory 2380. In one embodiment, the externalinterface 2312 and communication interface 2390 physically couple to oneanother to transmit data through a wire, bus, and/or electrical contactconnection. Such a connection may also serve to physically secure theexternal processing device 2302 to the application specific accessory2380. Alternatively, or in addition to such a wired connection, theexternal interface 2312 may transmit and receive data to the applicationspecific accessory 2380 wirelessly, using for example a Bluetoothstandard, or any one of the 802.11 standards.

The power cell module 2316 is an optional module that may comprise thepower cell 1404, charge level indicator 1410, recharging module 1704,and switch 1412 of FIG. 17. The power cell module 2316 and itscomponents may perform some or all of the functions of the battery packdescribed in FIGS. 1-22. For example, the power cell module 2316 mayprovide power to the mobile device 2350 through the internal interface2310 via the power bus 2322. The power cell module 2316 may also providepower to the application specific accessory 2380 through the externalinterface 2312 via the power bus 2322.

The memory circuit 2304 may comprise volatile and/or non-volatilestorage devices for storing an operating system 2324, softwareapplications 2326, and/or data. In one example, the memory circuit 2304may comprise one or more independent computer data storage devices, suchas, but not limited to, FLASH memory, ROM, RAM, hard disks, opticaldisks, and the like. The operating system (OS) 2324 can be any type ofOS that adequately manages and coordinates the activities and sharing ofthe external processing accessory's 2302 resources, such as, but are notlimited to, Android™, iPhone OS™, Symbian OS™, BlackBerry OS™, WindowsMobile™, Linux, Palm webOS™, and Maemo™. The OS 2324 may also host avariety of computing applications that are resident on memory circuit2304.

In one embodiment, the memory circuit 2304 may include one or moresoftware applications 2326 (also referred to as firmware) that are eachassociated with an application specific accessory 2380. For example, thememory circuit 2304 may contain an application 2326 specific to aglucose level measuring accessory, that when executed by the processors2306 a, 2306 b, controls the glucose level measure accessory deviceand/or the external processing accessory 2302. The application 2326controls the hardware associated with the application specific accessory2380 and the external processing accessory 2302 and may controltransmission and reception of data with the mobile device 2350. Forexample, the application 2326 when executed may cause the externalinterface 2312 to receive data from the communications interface 2390 ofthe application specific accessory 2380. The application 2326 may thencause the data to be processed by the processors 2306 a, 2306 b. Theprocessed data may then be transmitted to the mobile device 2350 fordisplay on the output interface 2362 (e.g., a display) of the mobiledevice 2350. The application 2326 may also control the internalinterface 2310 to receive data from the mobile device 2350 in responseto user interaction with the input interface (e.g., a keyboard) 2362 ofthe mobile device 2350.

In one embodiment, an application 2326 associated with a givenapplication specific accessory 2380 is executed by the processor 2306 aupon detection of the associated application specific accessory 2380.That is, the external processing accessory 2302 and/or the applicationspecific accessory 2380 contains circuitry that allows for the automaticdetection of a particular application specific accessory 2380 when it iscoupled to the external processing accessory 2302 or otherwise turnedon. When the application specific accessory 2380 is detected, theassociated application 2326 of the application specific accessory 2380is executed within the external processing accessory 2302 by one or moreof the processors 2306 a, 2306 b. For example, in one embodiment, one ormore of the pins of the external interface 2312 detects an identitycircuit 2396 (See FIG. 23B) located within the applications specificaccessory 2380 upon connection to the communication interface 2390. Theidentify circuit 2394 may comprise, for example, resistors and/orcapacitors that have values uniquely associated with the specificapplication specific accessory 2380. The unique resistance and/orcapacitance value associated with each application specific accessory2380 allows the external processing accessory 2302 to determine whichapplication(s) to execute upon connection and detection of a particularapplication specific accessory 2380. In other embodiments, the identitycircuit 2394 may comprise identity information that is stored withinmemory, such as memory circuit 2382, and transmitted to the externalprocessing accessory 2302 upon connection.

In one embodiment, the plurality of applications 2326 hat are associatedwith application specific accessories 2380 may be stored on the memorycircuit 2304 near the time of production of the external processingaccessory 2302. In other embodiments, applications may be downloadedonto the memory circuit 2304 of the external processing accessory 2302at a later time via the internal interface 2310 and/or one of the I/Ointerfaces 2308 a, 2308 b. In yet other embodiments, the application2326 may be stored within the memory 2382 of the application specificaccessory 2380 and transferred to the external processing accessory 2302for storage and/or execution when the application specific accessory2380 is coupled to the external processing accessory 2302. Updates tothe applications 2326 may be downloaded to the external processingaccessory 2302 by any of the above ways.

The cryptography module 2314 of the external processing accessory 2302may serve to encrypt and/or decrypt data sent wirelessly or by wirebetween the internal interface 2310 and the mobile device interface2360. The cryptography module 2314 may also serve to encrypt and/ordecrypt data sent wirelessly or by wire between the external interface2312 and the communication interface 2390 of the application specificaccessory 2380. Various types of data encryption techniques may beutilized that are well known in the art including: symmetric-keycryptography such as Data Encryption Standard (DES), Advanced EncryptionStandard (AES), hashing functions (MD5, SHA-1, SHA-2, SHA-3, etc.); andasymmetric-key cryptography such as digital signature schemes like theRivest, Shamir and Adleman (RSA) algorithm and the Digital SignatureAlgorithm (DSA). The cryptography modules 2314 and 2352 may beimplemented using hardware circuitry, software, or both.

Referring to FIG. 23B, the application specific accessory 2380 maycomprise a memory circuit 2382, a processing circuit 2386, an outputinterface 2388, a communication interface 2390, one or more inputinterfaces 2392, an identity circuit 2394, and a bus 2396. The buscommunicatively couples the memory 2382, the processing circuit 2386,the output, input, and communication interfaces 2388, 2392, and 2390,and the identity circuit 2394 to one another. The communicationinterface 2390 allows for wireless or wire line communication with theexternal processing accessory 2302. The specific input interface 2392for a particular application specific accessory 2380 may vary widelydepending on the type of application specific accessory 2380. Forexample, a blood glucose level measuring accessory may have a receiveradapted to receive blood and measure its glucose level as one of itsinput interface 2392. A barcode reader accessory may have a barcodescanner as its input and output interface 2392, 2388 to read barcodes.

Ideally, the processing circuit 2386 and memory circuit 2382 of theapplication specific accessory 2380 are simple in design and low cost.The bulk of the processing and storing functions should ideally becarried out by the external processing accessory 2302 to minimize thecomplexity and cost of the application specific accessory 2380. Thus,the processing circuit 2386 and memory circuit 2382 of the applicationspecific accessory 2380 may perform only those functions necessary tocommunicate data received from the input interface 2392 and/or identitycircuit 2394 to the external processing accessory 2302 via thecommunication interface 2390. The processing circuit 2386 and memorycircuit 2382 may also control the output interface 2388.

In one embodiment, the memory circuit 2382 stores applications 2384associated with the application specific accessory 2380. Theapplications 2384 may be transmitted to the external processingaccessory 2302 upon connection to the external processing accessory2302. The external processing accessory 2302 may then execute theapplications 2384 to control communication and operation of theapplication specific accessory 2380, and transmit any received and/orprocessed data to the mobile device 2350. In some embodiments, one ormore of the applications 2384, may be executed on the processing circuit2386 of the application specific accessory 2380 to control hardwarecomponents of the application specific accessory 2380.

A software development kit (SDK) may also be provided to a potentialmanufacturer of an application specific accessory 2380. The manufacturermay use the SDK to create unique applications 2326 for a givenapplication specific accessory 2380. The SDK 2326 may include such toolsas, but not limited to, a source code editor, a compiler, buildautomation tools, a debugger, and other utilities that may be presentedin an integrated development environment (IDE). The SDK allows users andpotential manufacturers to create a variety of unique applications forapplication specific accessories 2380 that are executed on the one ormore processors 2306 a and 2306 b, and may also utilize the varioustypes of resources available on a particular embodiment of the externalprocessing accessory 2302.

Payment Processing Mobile Accessories

Magnetic Strip Card Reader Embodiment

In other embodiment, an accessory for a mobile device is described thatallows the mobile device to receive and process payment transactionsfrom a magnetic strip credit card and/or “smart card” (RFID contact orcontactless) based payment card. FIG. 24 illustrates a functional blockdiagram of one embodiment of a payment processing mobile accessory 2402(also referred to as a “payment processing accessory 2402”) adapted toread data stored on one or more magnetic strips associated with apayment card. The payment processing accessory 2402 may comprise amemory circuit 2404, a magnetic strip reader processing circuit 2406, amagnetic strip reader interface 2408, an internal interface 2410, acryptography module 2412, and a bus 2413. The bus 2413 allows forcommunication between the memory circuit 2404, the magnetic strip readerprocessing circuit 2406, the magnetic strip reader interface 2408, theinternal interface 2410, and the cryptography module 2412.

The memory circuit 2404 may comprise volatile and/or non-volatilestorage devices for storing an operating system 2414, softwareapplications 2416 (including firmware), and/or data. The memory circuit2404 my comprise one or more independent computer data storage devices,such as, but not limited to, flash memory, ROM, RAM, hard disks, opticaldisks, solid-state memory such as flash memory, or any other computerdata storage known in the art. The operating system (OS) 2414 can be anytype of OS that adequately manages and coordinates the activities andsharing of the payment processing accessory's 2402 resources, such as,but are not limited to, Android™, iPhone OS™, Symbian OS™, BlackBerryOS™, Windows Mobile™, Linux, Palm webOS™, and Maemo™. The OS 2414 mayalso host a variety of applications 2416 that are resident on memorymodule 2404. The applications 2416, when executed by magnetic stripreader processing circuit 2406, may control operation of the paymentprocessing accessory 2402. For example, the application 2416 may controlhow and when payment data is received from the magnetic strip readerinterface 2408, how that data is processed, and how it is transmitted tothe mobile device 2450 for further processing.

The cryptography module 2412 of the payment processing accessory 2402may serve to encrypt and/or decrypt any data received or transmittedwirelessly or by wire from the internal interface 2410 to the mobiledevice interface 2460. The cryptography module 2412 may also serve toencrypt and/or decrypt any data received from the magnetic strip readerinterface. For example, at some point after receiving data associatedwith a payment card from the magnetic strip reader interface, thecryptography module 2412 may encrypt the received data with anencryption scheme before transmitting the data to the mobile device2450. The encrypted data may then be transmitted to a merchant accountprovider for decryption and approval. Various types of data encryptiontechniques may be utilized including: symmetric-key cryptography such asDES, AES, hashing functions (MD5, SHA-1, SHA-2, SHA-3, etc.); andasymmetric-key cryptography such as digital signature schemes like RSAand DSA. The cryptography modules 2412 and 2468 may be implemented usinghardware circuitry, software, or both.

In one embodiment, a private and public key pair may be shared between amerchant account provider and the payment processing accessory 2402.Specifically, the merchant account provider that issues the paymentcards stores the private key within its system and keeps this keysecure. The merchant account provider may then distribute acorresponding public key to the payment processing accessory 2402, whichmay be stored on the memory circuit 2404. The cryptography module 2412may then use the public key stored to sign/encrypt data associated witha payment card received from the magnetic strip reader interface 2408.The signed data may then be securely transmitted to the mobile device2450 which then transmits the account information and purchase amount tothe merchant account provider for decryption and approval. In oneembodiment, the public key may be programmed into the memory 2404 nearthe time the accessory 2402 is manufactured. In other embodiments, thepublic key may be transmitted to the accessory 2402 via a mini-USBinterface 2702 (see FIG. 27A). In yet other embodiments, the public keymay be transmitted to the accessory 2402 by the mobile device 2450through the internal interface 2410.

The magnetic strip reader interface 2408 is configured to read magneticstrips on various payment cards, such as credit cards, debit cards,charge cards, pre-paid credit cards, and/or any other card based paymentsystems that utilize magnetic strips. Magnetic strip reader interface2408 can be, for example, capable of reading standard three-track stripcards following the ISO/IEC standard 7811.

The magnetic strip reader interface 2408 is configured to read accountinformation and other data associated with a magnetic strip payment card(hereinafter referred to as a “Magcard”). In one example, accountinformation and other data received from the Magcard is read by themagnetic strip reader interface 2408 in connection with and/or tofacilitate a purchase transaction. For example, upon swiping a Magcardthrough the magnetic strip reader interface 2408, the accountinformation and other data is received by the magnetic strip readerinterface 2408 and transmitted via the bus 2413 to the magnetic stripreader processing circuit 2406 for processing. The processing circuit2406 may execute one or more applications 2416 stored within the memory2404 to carry out specific tasks in connection to facilitating thepurchase transaction. For example, the magnetic strip reader processingcircuit 2406 may control the magnetic strip reader interface 2408 toreceive the account information and the other data. The processingcircuit 2406 may then process the data by confirming its authenticity(valid bit string length, unexpired card, etc.). The processing circuit2406, in conjunction with the cryptography module 2412 may also encryptthe data received. The processing circuit 2406 may then process the datafor transmission to the mobile device 2450 through the internalinterface 2410. These steps may be performed automatically after theMagcard is swiped through the magnetic strip reader interface 2408.

In other embodiments, the account information and other data may also betransmitted via the bus 2413 to the memory module 2404 for storage. Inone example, the magnetic strip reader processing circuit 2406 may be aprogrammable logic array that processes account information and otherdata directly received from the magnetic strip reader interface 2408.

In one embodiment, the mobile device 2450 may execute a paymentprocessing application 2458 on the mobile device processing circuit 2454to receive and process the account information and other data receivedfrom the payment processing accessory 2402. The payment processingapplication 2458 may be a unique application specially developed by aparticular merchant account provider using a software development kit(SDK) provided to the merchant account provider by the manufacturer ofthe payment processing accessory 2402. The application 2458, onceexecuted, may allow a user of the mobile device 2450 to enter detailedinformation related to the particular purchase transaction. For example,the user may be prompted to enter purchase amount information, a cardholder's signature, date of transaction, etc. into an input interface2452, such as a keyboard, touch-screen display, etc., of the mobiledevice 2450. Other information may also be entered such as any securitypasswords necessary to proceed with the transaction, for example, a PINknown to either the card holder or the merchant processing thetransaction.

Once the necessary account information and other data has been receivedby the mobile device 2450 from the payment processing accessory 2402,and any details regarding the purchase amount have been entered, thetransmission and receive (Tx/Rx) circuit 2464 of the mobile device 2450may wirelessly transmit the account information (e.g., credit cardnumber) and purchase transaction information (e.g., transaction amount,etc.) through the mobile device's wireless network to the merchantaccount provider for approval. The Tx/Rx circuit 2464 of the mobiledevice 2450 may also receive an acknowledgment message from the merchantaccount provider that the charge was approved (or another message thatit was declined). The acknowledgment message may be communicated to thepurchaser or merchant via the output interface 2466 of the mobile device2450.

Upon approval, a receipt detailing the transaction may be generated bythe mobile device 2450. A signature of the card holder may also beentered through the input interface 2452 of the mobile device tovalidate the transaction. The receipt information along with anysignature may be transmitted wirelessly, or by wire contact, to a localprinter for printing. In other embodiments, an email address associatedwith the purchaser or the Magcard may be entered into the mobile device2450 via the input interface 2452. Then, upon approval of thetransaction the receipt can be emailed to the email address entered bythe mobile device 2450. In yet, other embodiments, a receipt detailingthe transaction may be generated either before or after a signature isacquired from the purchaser via the input interface 2452.

In other embodiments, a user may start a purchase transaction bylaunching the payment processing application 2458 on the mobile device2450 to initialize the payment processing accessory 2402. The processingcircuit 2454 may then execute the application 2458 to generate a readrequest signal that is transmitted to the magnetic strip readerprocessing circuit 2406 through the mobile device interface2460—internal interface 2410 connection. Once the processing circuit2406 of the payment processing accessory 2402 receives the read requestsignal, it initializes the magnetic strip reader interface 2408 to enteran idle state that is ready to receive account information and otherdata from a Magcard. In the idle state, the magnetic strip readerinterface 2408 will receive the data once a Magcard is swiped. When noread request signal is present, or has not been received in a given timeperiod, hardware components within the payment processing accessory 2402may be turned off or put in a lower power standby mode therebyminimizing power consumption by the payment processing accessory 2402when no purchase transaction is expected.

If during the idle state, a Magcard is swiped through the magnetic stripreader interface 2408, the processing 2406 receives the accountinformation and associated data of the Magcard and may process, encrypt,and/or store the data as discussed above. The data may also betransmitted to the mobile device 2450 for completion of the purchasetransaction as discussed in the embodiment above.

In other embodiments, the payment processing accessory 2402 may do morethan read information from a Magcard and provide it to the mobile device2450 for processing a purchase transaction. For instance, in cases wherethe mobile device may not have a connection to a network through which atransaction can be validated (e.g., through which a credit card paymentcan be approved), the payment processing accessory 2402 may itselfinclude a wireless connection that is capable of communicating with amerchant account provider to validate the transaction. In someimplementations, the payment processing accessory 2402 may be powered bythe mobile device 2450 via the internal interface 2410, while in otherimplementations the payment processing accessory 2402 may have its owninternal power source (e.g., power cell module 2316 in FIG. 23A).

In yet other implementations, the payment processing accessory 2402 mayinclude an input device to authenticate the user of the Magcard. Forexample, the payment processing accessory 2402 may include a fingerprint scanner that collects the payor's finger print and provides it tothe mobile device 2450 via the internal interface 2410. The finger printinformation may be subsequently sent to a merchant account provider forverification as part of authenticating the payment using the Magcard.

It should be understood that the payment processing accessory 2402 isnot limited to just a magnetic card reader. In various implementationsthe payment processing accessory 2402 may include a smart card,proximity reader, and/or bar code scanner adapted to collect informationfrom a payor's payment card.

FIG. 25 illustrates a perspective view of one embodiment of the paymentprocessing accessory 2402. In this example, the payment processingaccessory 2402 comprises a casing or holster that is shaped to receiveor house a mobile device within a cavity 2510. The cavity 2510 may becontoured to match the outer shape of the particular mobile device thepayment processing accessory 2402 is intended to mate with and providepayment card transaction processing capabilities to. FIG. 25 illustratesthe internal interface connector 2410 that couples to the correspondingmobile device interface 2460 for the transmission of data between theaccessory 2402 and mobile device 2450. The internal interface connector2410 may snap or lock into place with the mobile device interface 2460to provide a secure physical connection between the accessory 2402 andmobile device 2450.

The payment processing accessory 2402 may include one or more openings2512, 2514, 2516, and 2518 to facilitate access to various features ofthe mobile device. For instance, a first opening 2512 may allow anunobstructed view for a camera lens on the back of the mobile device. Asecond opening 2514 may provide access to a screen on/off switch for themobile device. A third opening 2516 may provide access to an audio jackon the mobile device. A fourth opening 2518 may provide access to avolume control sliding switch.

FIG. 26 illustrates a front view of the payment processing accessory2402 of FIG. 25. The payment processing accessory 2402 includes a backplane 2602, first and second sides 2604 and 2606, a bottom side 2608,and a top side 2610. The back plane 2602, first and second sides 2604and 2606, bottom side 2608, and top side 2610 may be shaped to form apocket or cavity 2510 in which a mobile device can be housed. The topside 2610 of the payment processing accessory 2402 may slide out toallow insertion and removal of the mobile device.

Referring back to FIG. 25, the payment processing accessory 2402comprises a bottom section 2502 and a top section 2504 that can beseparated from each other to allow a mobile device to be inserted withinthe cavity 2510. The two sections can then be coupled together to securethe mobile device in place. The payment processing accessory 2402 alsocomprises a magnetic strip swiping region 2506 within which the magneticstrip reader interface is housed. The magnetic strip reader interface isconfigured to read Magcard account information and other data associatedwith the Magcard. The magnetic strip reader interface obtains thisinformation when the Magcard is swiped through the magnetic stripswiping region 2506 causing the magnetic strip of the Magcard containingaforementioned data to come into contact with the magnetic strip readerinterface.

In the embodiment shown, the magnetic strip swiping region 2506 islocated along the bottom side 2608 of the mobile device 2450. Thisfeature allows a user to conveniently hold the mobile device and paymentprocessing accessory 2402 in his/her palm along the first and secondsides 2604 and 2606, while sliding a Magcard along the magnetic stripswiping region 2506. In this fashion the magnetic strip swiping region2506 is not obstructed by the user's hand when the payment processingaccessory 2402 housing the mobile device is held is held along the firstand second sides 2604 and 2606.

The circuits and/or components of the payment processing device 2402 maybe housed within the bottom section 2502 and/or top section 2504. Forexample, the magnetic strip reader processing circuit 2406 and magneticstrip reader interface 2408 may be housed within the bottom section2502. A power cell module 2316 may be housed within the thickness of theback plane 2602 of the top section 2504.

FIGS. 27A and 27B illustrate perspective views of a mobile device 2450housed within the casing of the payment processing accessory 2402. Ascan be appreciated from the figures, the payment processing accessory2402 is shaped to closely wrap around the mobile device 2450, and servesas a protective case for the mobile device 2450. FIGS. 27A and 27Billustrate how a credit card may be swiped through the magnetic stripswiping region 2506. FIG. 27A illustrates an embodiment of the paymentprocessing accessory 2402 that features a mini-USB interface 2702 forcharging of the battery of the mobile device 2450, and/or providingcommunication with the payment processing accessory 2402. FIG. 27Billustrates how an interface cable may be connected to the mini-USBinterface 2702 to charge the mobile device 2450 and/or communicate withpayment processing accessory 2402.

FIG. 28 illustrates a bottom view of the payment processing accessory2402. FIG. 29 illustrates a side view of the payment processingaccessory 2402. FIGS. 28 and 29 illustrate a measurement d thatrepresents the maximum depth of the casing of the payment processingaccessory 2402 (also referred to as the thickness of the paymentprocessing accessory 2402). In one embodiment, the depth d is designedto be as thin as possible so that the overall depth/thickness of themobile device 2450 and payment processing accessory 2402, together isnot substantially more than the depth/thickness of the mobile device2450 by itself. In one embodiment, the depth d of the payment processingaccessory 2402 is less than the depth/thickness of the mobile device2450 plus 0.25 inches. In another embodiment, the depth d of the paymentprocessing accessory 2402 is less than the depth/thickness of the mobiledevice 2450 plus 0.125 inches. In another embodiment, the depth d of thepayment processing accessory 2402 is less than 1 inch. In yet anotherembodiment, the depth d of the payment processing accessory 2402 is lessthan 0.75 inches. In yet other embodiments, the depth d of the paymentprocessing accessory 2402 is less than 0.5 inches. By having a thindepth/profile, the payment processing accessory 2402 housing the mobiledevice 2450 can be conveniently stored, for example, in the pocket ofthe user. Payment processing accessories for mobile devices that have asubstantially thicker depth/profile cannot comfortably be stored in thepocket of a user.

FIG. 30 illustrates the payment processing accessory 2402 of FIG. 25 inan open configuration where the top section 2504 and a bottom section2502 have been separated. The top section 2504 and the bottom section2502 may come apart to allow the mobile device 2450 to be inserted intothe cavity 2510. The top and bottom section 2504 and 2502 may then besecured to one another to secure the mobile device 2450 within thecavity 2510. In one embodiment, the top section 2504 may include afemale connector groove 3004 that receives a male connector rail 3002 ofthe bottom section 2502. The mail connector rail 3002 is configured tofit inside the female connector groove 3004 to secure the top section2504 to the bottom section 2502. In this manner, the top section 2504can be coupled to the bottom section 2502 by pressure fit.

FIG. 31 illustrates the payment processing accessory 2402 with anexploded view of the bottom section 2502. For example, the bottomsection 2502 may comprise an inner section 3102, an outer section 3104,the mini-USB interface 2702, the magnetic strip reader interface 2408,and the internal interface 2410. The inner section 3102 and outersection 3104 form a top and bottom shell in between which the mini-USBinterface 2702 and the magnetic strip reader interface 2408 aresubstantially housed. A portion of the internal interface 2410 is alsohoused within the inner section 3102 and outer section 3104.Consequently, the mini-USB interface 2702, the magnetic strip readerinterface 2408, and the internal interface 2410 may be housed within thethickness of the bottom section 2502 of the payment processing accessory2402.

FIG. 32A illustrates a perspective view of the internal contents of thebottom section 2502, including, for example, the magnetic strip readerinterface 2408, the internal interface 2410, and the mini-USB interface2702. FIG. 32B illustrates a perspective view of the magnetic stripreader interface contact points 3202 to which the magnetic strip readerinterface 2408 may secure to. FIG. 32C illustrates a perspective view ofthe mounting rails 3204 that secure the magnetic strip reader interfacecontact points 3202, the magnetic strip reader interface 2408, theinternal interface 2410, and the mini-USB interface 2902.

In other embodiments, the payment processing accessory 2402 may beadapted to have an additional interface that is configured to read “chipand pin” based payment systems, such as, but not limited to, “smartcards.” In yet other embodiments, the payment processing accessory 2402may be adapted to have yet another interface that is configured to readradio frequency identification (RFID) tags that are associated with anelectronic payment system of a merchant account provider. In yet otherembodiments, the payment processing accessory 2402 may comprise only oneof or any combination of: a magnetic card reader interface, chip and pinreader interface, and/or RFID reader interface.

Smart Card Reader Embodiment

FIG. 33 illustrates a functional block diagram of another embodiment ofa payment processing mobile accessory 3302 adapted to read data storedon an integrated chip embedded into a payment card, such as a “smartcard” and/or contactless (near field communication) smart card. Thepayment processing accessory 3302 may comprise a memory module 3304, asmart card reader processing circuit 3306, a smart card reader interface3308, an internal interface 3310, an encryption module 3312, and a bus3313. The bus 3313 allows for communication between the memory module3304, the smart card reader processing circuit 3306, the smart cardreader interface 3308, the internal interface 3310, and the encryptionmodule 3312.

The steps and functions performed by the payment processing accessory3302 may be very similar to those described in relation to the magneticpayment processing accessory 2402 in FIG. 24. The memory module 3304 maycomprise an operating system 3314, and one or more applications 3316.The memory module 2404 may comprise one or more independent computerdata storage devices, such as, but not limited to, flash memory, ROM,RAM, hard disks, optical disks, and the like. The operating system (OS)3314 can be any type of OS that adequately manages and coordinates theactivities and sharing of the payment processing accessory's 3302resources, such as, but are not limited to, Android™, iPhone OS™,Symbian BlackBerry OS™, Windows Mobile™, Linux, Palm webOS™, and Maeme™.The OS 3314 may also host a variety of computing applications that areresident on memory module 3304.

The smart card reader interface 3308 may be configured to read accountinformation and other related data stored on a chip embedded intopayment card, such as a smart card. In one embodiment, the smart cardreader interface 3308 can be configured to accept and read data from asmart card featuring electrical contacts. In another embodiment, thesmart card reader interface 3308 can be configured to accept and readdata from a contactless smart card. In such an embodiment, the smartcard reader interface uses radio-frequency waves to communicate with thechip embedded within the contactless smart card. In either embodiment,account information and/or other related data stored on the chip withinthe smart card is read by the smart card reader interface 3308.

Once the account information and/or other data has been received by themobile device 3350 from the payment processing accessory 3302, and anydetails regarding the purchase amount and a user pin have been entered,the transmission and receive (Tx/Rx) circuit 3364 of the mobile device3350 may wirelessly transmit the account information, pin information,and purchase transaction information through its wireless network to themerchant account provider for approval. The Tx/Rx circuit 3364 of themobile device 3350 may also receive an acknowledgment message from themerchant account provider that the charge was approved. Theacknowledgment message may be communicated to the purchaser or merchantvia the output interface 3366 of the mobile device 3350.

Upon approval, a receipt detailing the transaction may be generated bythe mobile device 3350. The receipt information may be transmittedwirelessly, or by wire contact, to a local printer for printing. Inother embodiments, an email address associated with the purchaser or thesmart card may be entered into the mobile device 3350 via the inputinterface 3352. Then, upon approval of the transaction the receipt canbe emailed to the email address entered by the mobile device 3350. Inyet, other embodiments, a receipt detailing the transaction may begenerated either before or after a signature is acquired from thepurchaser via the input interface 3352.

Note that, in some implementations, a payment processing accessory mayinclude a combination of payment input interfaces, such as a smart cardreader interface 3308, a magnetic strip reader interface 2408, and/orother types of payment input interfaces.

Near Field Communication Accessory

In another embodiment, FIG. 34 illustrates a near field communication(NFC) accessory 3402 for a mobile device 3450. The NFC accessory 3402 iscapable of communicating with ISO/IEC 14443 smartcards and readers, aswell as with other NFC devices, thereby equipping the mobile device 3450with NFC capability. The NFC accessory 3402 may comprise a processingcircuit 3403, a memory circuit 3404, an NFC transmitter 3406, an NFCreceiver 3408, an internal interface 3410, a cryptography module 3412, apower cell module 3414, an external interface 3416, a data bus 3418, anda power bus 3420. The data bus 3418 communicatively couples theprocessing circuit 3403, the memory circuit 3404, the NFC transmitter3406, the NFC receiver 3408, the internal interface 3410, thecryptography module 3412, the power cell module 3114, and the externalinterface 3416.

The NFC accessory 3402 may transmit to and receive data from the mobiledevice 3450. Specifically, the internal interface 3410 of the NFCaccessory 3402 communicatively couples to the mobile device interface3460 of the mobile device 3450. In one embodiment, the internalinterface 3410 and mobile device interface 3460 physically couple to oneanother to transmit data through a wire, bus, and/or electrical contactconnection. Such a connection may also serve to physically secure theNFC accessory 3402 to the mobile device 3450. Alternatively, or inaddition to such a wired connection, the internal interface 3410 maytransmit and receive data to the mobile device 3450 wirelessly using,for example, a Bluetooth standard, or any one of the 802.11 standards.

The power cell module 3414 is an optional module that may comprise thepower cell 1404, charge level indicator 1410, recharging module 1704,and switch 1412 of FIG. 17. The power cell module 3414 and itscomponents may perform some or all of the functions of the battery packdescribed in FIGS. 1-22. For example, the power cell module 3414 mayprovide power to the mobile device 3450 through the internal interface3410 via the power bus 3420, and/or power the NFC accessory 3402.

The memory circuit 3404 may comprise volatile and/or non-volatilestorage devices for storing an operating system, software applications,and/or data. In one example, the memory circuit 3401 may comprise one ormore independent computer data storage devices, such as, but not limitedto, flash memory, ROM, RAM, hard disks, optical disks, and othercomputer data storage devices known in the art. The operating system(OS) can be any type of OS that adequately manages and coordinates theactivities and sharing of the NFC accessory's 3402 resources, such as,but not limited to, Android™, iPhone Symbian OS™, BlackBerry OS™,Windows Mobile™, Linux, Palm webOS™, and Maemo™. The OS may also host avariety of computing applications that are resident on memory circuit3404.

The cryptography module 3412 of the external processing accessory 3402may serve to encrypt and/or decrypt data sent wirelessly or by wirebetween the internal interface 3410 and the mobile device interface3460. Various types of data encryption techniques may be utilized thatare well known in the art including: symmetric-key cryptography such asDES, AES, hashing functions (MD5, SHA-1, SHA-2, SHA-3, etc.); andasymmetric-key cryptography such as digital signature schemes like RSAand DSA. The cryptography modules 3412 and 3452 may be implemented usinghardware circuitry, software, or both.

The NFC transmitter 3406 and NFC receiver 3408 are responsible fortransmitting and receiving, respectively, data to and from anothertarget NFC device (also referred to as an external NFC device) usingnear field communication. The transmitter 3406 and receiver 3408 mayutilize magnetic field induction to communicate with the target NFCdevice over a short distance, such as, 20 centimeters. The NFC accessory3402 can communicate with both existing ISO/IEC 14443 smartcards andreaders, as well as with other NFC devices. The transmitter 3406 andreceiver 3408 may operate in either a passive communication mode or anactive communication mode. Various types of data may be exchangedbetween the NFC accessory 3402 and the target NFC device.

For example, in one embodiment, an application executed on the mobiledevice 3450 allows a user to enter in payment card information, such as,credit card numbers, debit card numbers, and information associated witheach payment card such as, expiration dates, PIN numbers, billingaddresses, etc. via an input interface 3456. The data entered may bestored on the mobile device memory 3462 (which may also store theapplication executed), and/or transmitted to the NFC accessory 3402 viathe mobile device interface 3460 and internal interface 3410 connection.The processing circuit 3403 of the NFC accessory 3402 may receive thepayment card data for each payment card and program the NFC transmitter3406 with the payment card data and associated information.

A user then desiring to make a payment with one of the stored cards mayselect a card (e.g., through the application on the mobile device 3450)and request that the NFC transmitter 3406 transmit the payment card datato another NFC device responsible for receiving the payment card data.The other NFC device may be pay station that receives and processespayment. For example, the other NFC device may transmit the payment datato a merchant account provider that processes the payment and approvesthe transaction. The NFC device may then communicate an acceptancemessage (or denial) to the NFC accessory 3402, which receives thecommunication via the NFC receiver 3408. The acceptance or denialmessage may then be transmitted to the mobile device 3450 from the NFCaccessory 3402 for any further processing. In one embodiment, thecryptography module 3412 encrypts the payment card data prior totransmission of the data by the NFC transmitter 3406.

In this manner, the combination of the mobile device 3450 and NFCaccessory 3402 may serve as an “electronic wallet” whereby a user mayavoid having to carry a multitude of physical credit cards. This schememay also provide improved security over traditional credit cards sincethe application may request the user to authenticate themselves by, forexample, entering a password or PIN prior to clearance of thetransaction.

In another embodiment, an application on either the mobile device 3450or the NFC accessory 3402 keeps track of all such payment transactionsand logs information related to the payment transactions to generateexpense reports and the like. For example, the application may storetime, date, and purchase price information for all payment cardtransactions that take place. This may assist a user later by having aconvenient record of where each transaction took place and how much itwas for. For example, a user on a business trip may keep track of allbusiness related expenses and print out the expense report forreimbursement. The application may also utilize GPS hardware resident onthe mobile device 3450 or within the accessory 3402 to monitor exactlywhere the transactions took place. In this fashion, the application canstore the time, date, purchase price, and location information for allpayment transactions executed. By further utilizing informationavailable on the internet, the application can make an educated guess asto what specific retailer the transaction was executed at by crossreferencing the GPS coordinates with a public directory of businessesaccording to a map.

In another embodiment, the NFC accessory 3402 may provide the mobiledevice with payment processing capabilities. Specifically, the NFCreceiver 3408 may receive data associated with a payment card, such ascredit card numbers, expiration date, etc. from another NFC device suchas a smart card based credit card. In another embodiment, the NFCaccessory 3402 my receive data associated with a coupon from an NFCenabled billboard. For example, an NFC capable kiosk or advertisingstation may store a plurality of coupon data that is available fordownload. A user of the NFC accessory 3402 may place the NFC accessory3402 near the advertising station so that the NFC receiver 3408 mayreceive and download coupon data using near field communication. The NFCaccessory 3402 may then store the coupon data within its memory 3404and/or transmit it to the mobile device 3450 for storage and/or displayof the information acquired to the user.

In another embodiment, the NFC accessory 3402 may transmit coupon datato another NFC device. For example, coupon data that was previouslyacquired from an advertising station as discussed above may then beredeemed by transmitting the coupon data to a coupon data receiver at,for example, the cashier of the merchant associated with the coupon. Thecoupon data may also have been acquired from the intern& For example,the mobile device 3150 may connect to the internet and download coupondata from a merchant's website and then transmit this data using the NFCtransmitter 3406 to receiving NFC device for redemption.

In another embodiment, the NFC accessory 3402 may be programmed to storeaccess key card information used to open doors and gain access to areasrestricted by NFC door locks. Thus, a user would not have to carryaround a plurality of NFC access cards. Instead, the user may programall such access card information onto the NFC accessory 3402 and use theNFC accessory 3402 to transmit this information to gain access torestricted areas.

In another embodiment, the NFC accessory 3402 may be programmed to storepublic transportation account information that allows a user to gainaccess to a subway car or other public transportation system. Forexample, the NFC transmitter 3406 may transmit public transportationaccount information such as travel credit to an NFC kiosk at the publictransportation station. The NFC kiosk is configured to receive thetravel credit, deduct it from the user's balance, and allow the useraccess to the public transportation system.

The NFC accessory 3402 can be programmed to store a plethora ofinformation that can later be transmitted to another NFC devicereceiver. Other such uses may include programming plane or train ticketinformation onto the NFC accessory 3402 for expedited processing at theairport or train station; programming user identification and/orpassport information to the NFC accessory 3402; and purchasing andreceiving event tickets from a kiosk or transmitting event ticketinformation for redemption.

Television Signal Receiver and Battery Pack Mobile Accessory

In another embodiment, a television signal receiver accessory for amobile device is disclosed. FIG. 35 illustrates a functional blockdiagram of a television signal receiver and battery pack mobileaccessory 3502 (hereinafter “TV receiver accessory 3502”). The TVreceiver accessory 3502 may comprise a TV signal receiver 3504, a TVsignal processor 3506, a TV signal transmitter 3503, a service providertransmitter 3507 an external interface 3508, an internal interface 3510,a power cell module 3512, a data bus 3514, and/or a power bus 3516. Thedata bus 3514 may allow for communication between the TV signal receiver3504, TV signal transmitter 3503, TV signal processor 3506, serviceprovider transmitter 3507, the external interface 3508, the internalinterface 3510, and/or the power cell module 1512.

The power cell module 3512 is an optional module that may comprise thepower cell 1404, charge level indicator 1410, recharging module 1704,and switch 1412 of FIG. 17. The power cell module 3512 and itscomponents perform all the functions of the battery pack describedabove. For example, the power cell module 3512 may provide power to themobile device 3550 through the internal interface 3510 via the powerpath 3516. The power cell module 3512 may also power the hardwarecomponents of the TV receiver accessory. The power cell module 3512 mayalso recharge the battery of the mobile device 3550 through the internalinterface 3510 via the power path 3516.

The TV receiver accessory 3502 may be configured to receive and processanalog and/or digital television signals, and transmit the televisionsignal data to the mobile device 3550 for viewing on the mobile deviceoutput display 3562. In one embodiment of the TV receiver accessory3502, the TV signal receiver 3504 is configured to receive various typesof television transmission signals. The TV signal receiver 3504 maycomprise one or more antenna adapted for such a task. These televisionsignals received may include, but are not limited to, one or more of thefollowing: locally broadcast analog television signals, locallybroadcast digital television signals, satellite digital multimediabroadcasting (S-DMB) signals, terrestrial digital multimediabroadcasting (T-DMB) signals, 1 Seg signals, digital videobroadcasting—handheld (DVB-H or DVB-H2) signals, and MediaFLO basedsignals, such as FLOTV™ signals. In other embodiments, the TV signalreceiver 3504 may also be configured to receive satellite digital audioradio service (SDARS) signals, such as XM™ and Sirius™ signals. In yetother embodiments, the TV receiver accessory 3502 may compriseadditional circuitry and a separate antenna that is dedicated toreceiving SDARS signals.

After the TV signal receiver 3504 receives the TV signals, the TV signalprocessor 3506 may perform any required processing, such as decryption,filtering, and/or data conditioning. The processed data may then betransmitted to the mobile device 3550 for display on the mobile device'sdisplay 3562. The processed data may either be transmitted wirelessly bythe TV signal transmitter 3503 or by wire line connection through theinternal interface 3510. The TV signal transmitter 3503 may transmit thedata to a corresponding wireless receiver 3561 on the mobile device3550. For example, the TV signal transmitter 3503 may utilize aBlueTooth™ communication protocol, or any 802.11 wireless protocol. Thewireless link should have a bandwidth capable of transmitting audio andvideo signal components, including high definition video and soundsignals.

In another embodiment, the TV signals may be transmitted to the mobiledevice 3550 through a wire line connection via the internal interface3510 coupled to the corresponding mobile device interface 3560. Theinternal interface 3510 and the mobile device interface 3560 mayphysically and electrically couple to one another to facilitatetransmission and reception of data between the mobile device 3550 andthe TV receiver accessory 3502. This data may include the TV signalstransmitted from the TV receiver accessory 3502 to the mobile device,service order data (e.g., pay per view order requests) transmitted fromthe mobile device 3550 to the TV receiver accessory 3502, and also powerfrom the power cell module 3512 to the mobile device 3550.

The mobile device 3550 may comprise, among other things, a processingcircuit 3552, an input and output (I/O) interface 3554, a transmissionand receive (Tx/Rx) circuit 3556, memory 3558, the mobile deviceinterface 3560, a TV signal receiver 3561, a display 3562, and/or a bus3564. The bus 3564 may allow for communication between the processingcircuit 3552, the 110 interface 3554, the transmit and/or receive(Tx/Rx) circuit 3556, memory 3558, the mobile device interface 3560, thereceiver 3561, the display 3562, and/or other components of the mobiledevice 3550.

The processing circuit 3552 may receive the TV signals from the TVreceiver accessory 3502 (via either the receiver 3561 or mobile deviceinterface 3560), and perform further processing. For example, in oneembodiment, the mobile device's memory 3558 contains an application thatcan be executed by the processing circuit 3552 to further process thetelevision signal data received. The application may allow a user of themobile device 3550 to display a channel guide feature by which the usermay select a television program channel. The input interface 3554 may beused to select a channel, select recording options for recording selectprograms at select times, and change resolution and other displayfeatures. The processing circuit 3552 may also transmit the TV signalsto the display 3562 for viewing by a user of the mobile device 3550.

In one embodiment, the TV receiver accessory 3502 comprises a serviceprovider transmitter 3507 that allows the TV receiver accessory 3502 totransmit data to the service provider of the TV signals. For example, auser may choose to purchase certain programs (e.g., pay per viewprograms or movies) offered for purchase by the service provider. Theselection may be made via the I/O interface 3554 (e.g., a keyboard) onthe mobile device 3550 and transmitted to the TV receiver accessory3502. The TV receiver accessory may then transmit this purchase orderinformation to the service provider for processing.

In one embodiment, the user of the mobile device 3550 can utilize theTx/Rx circuit 3556 of the mobile device 3550 to communicate with atelevision signal service provider (e.g., FLOTV™) to order and/or payfor select services. Communication may be performed wirelessly andcarried out by the wireless network and/or service associated with themobile device 3550. Thus, pay per view services may be ordered utilizingthe transmitter circuit 3556 that the mobile device ordinarily uses formaking and placing calls or data transfers.

In another embodiment, the TV receiver accessory comprises a securitycircuit 3518 that is configured to identify a subscriber/user of the TVaccessory. For example, the security circuit may be a subscriberidentity module (SIM) card that is removably coupled to the TV receiveraccessory 3502 and contains a unique subscriber identity number. Thesecurity circuit 3518 may disable the TV receiver accessory if the SIMis not authenticated. For example, if a subscriber loses their TVreceiver accessory 3502 or does not financially maintain their account,the service provider can disable functionality of the TV receiveraccessory 3502 through the SIM card.

Thus, the TV receiver accessory 3502 allows a mobile device 3550 thatdoes not have an integrated television tuner or circuit to receive anddisplay over-the-air television signals (e.g., analog and/or digital).

Additional Features of the External Processing Accessory

Referring again to FIG. 23A, in various implementations the externalprocessing mobile accessory 2302 may comprise an input interface 2308 athat is configured to scan bar codes, such as, but not limited to,universal product codes (UPC) and two dimensional bar codes. Theprocessor 2306 a may process the data scanned by the bar code scanninginput interface 2308 a, and transmit the product information to themobile device 2350 via the internal interface 2310. An applicationresident on the mobile device's memory 2356 may enable the user of themobile device 2350 to identify the product/item scanned and carry outcertain functions including, updating inventory records, generatingpurchase/sale transactions, etc. In another embodiment, the externalprocessing accessory 2302 communicatively couples through externalinterface 2312 to an application specific accessory 2380 configured toscan such barcodes.

In another embodiment, the external processing mobile accessory 2302 maycomprise an input interface 2308 a that is configured to scan fingerprints. The processor 2306 a may process the finger print data scannedby the finger print reader input interface 2308, and transmit the fingerprint data to the mobile device 2350 via the internal interface 2310. Anapplication resident on the mobile device's memory 2356 may be executedby the processing circuit 2354 to identify the finger print scanned. Inone embodiment, the finger print scanned is compared to finger printdata stored in either memory module 2304 and/or the mobile device memory2356 for authentication. If the scanned finger print data matches fingerprint data stored then the user authentication is deemed successful andfunctionality of the mobile device 2350 is unlocked/allowed to the user.In another embodiment, the external processing accessory 2302communicatively couples through external interface 2312 to anapplication specific accessory 2380 configured to scan such finger printdata.

In another embodiment, the external processing mobile accessory 2302 maycomprise an input interface 2308 a that is configured to wirelesslyreceive restaurant menu information that is broadcast locally from adining establishment. The processor 2306 a may process the data receivedfrom the input interface 2308 a, and transmit the menu information datato the mobile device 2350 via the internal interface 2310. Anapplication resident on the mobile device's memory 2356 may be executedby the processing circuit 2354 to cause the menu to be displayed on themobile device's output interface 2362. In one embodiment, the user ofthe mobile device 2350 may then select one or more food or beverageitems, and/or make other requests, and this information may then betransmitted via an output transmitter interface 2308 b to a receiver ofthe dining establishment. In this fashion, a user can see the menu itemsavailable and order without the need for a menu or wait staff forassistance. In another embodiment, the external processing accessory2302 communicatively couples through external interface 2312 to anapplication specific accessory 2380 configured to receive such menuinformation broadcast, and transmit menu selection information to areceiver in the dining establishment for quicker order preparation.

Two Piece Casing for Mobile Accessories

All of the mobile device accessories disclosed herein, including forexample, the external processing accessory 2302, magnetic card paymentprocessing accessory 2402, smart card payment processing accessory 3302,NFC accessory 3402, and TV receiver accessory 3502 may be housed withina casing 3600 (also referred to as a holster) as shown in FIGS. 36-42.FIG. 36 illustrates a perspective view of one embodiment of the casing3600 in an open and a closed configuration. Specifically, the easing3600 may comprise a top section 3602 and a bottom section 3604 thatseparates to allow a mobile device to be housed within a cavity 3606.

FIG. 37 illustrates how a mobile device can be housed within the cavity3606 of the casing 3600. As can be appreciated from this figure, thecasing 3600 is shaped to closely wrap around the mobile device 3750, andserves as a protective case for the mobile device 3750.

FIG. 38 illustrates a front view of the casing 3600. The casing 3600includes a back plane 3802, first and second sides 3804 and 3806, abottom side 3808, a top side 3810, an internal interface 3812, and anend section 3820. The back plane 3802, first and second sides 3804 and3806, bottom side 3808 and top side 3810 may be shaped to form a pocketor cavity 3606 in which the mobile device 3750 may be housed. The topside 3810 of the casing 3600 may slide out to allow insertion andremoval of the mobile device 3750. The casing 3600 comprises a bottomend portion 3820 that may house within its thickness the hardwarecomponents of the various accessories 2302, 2402, 3302, 3402, and 3502.For example, the bottom end portion 3820 of the casing 3600 may housethe internal interface 2310, processors 2306 a, 2306 b, I/O interfaces2308 a, 2308 b, cryptography module 2314, memory circuit 2304, externalinterface 2312, power cell module 2316, the data bus 2320, and the powerbus 2322 of the external processing accessory 2302. In anotherembodiment, the bottom end portion 3820 of the casing 3600 may house theinternal interface 2410, cryptography module 2412, magnetic strip readerprocessing circuit 2406, magnetic strip reader interface 2408, memory2404, and the data bus 2413 of the magnetic strip payment processingaccessory 2402. In another embodiment, the bottom end portion 3820 ofthe casing 3600 may house the internal interface 3310, cryptographymodule 3312, smart card reader processing circuit 3306, smart cardreader interface 3308, memory circuit 3304, and the data bus 3313 of thesmart card payment processing accessory 3302. In another embodiment, thebottom end portion 3820 of the casing 3600 may house the internalinterface 3410, the cryptography module 3412, near field communicationprocessing circuit 3403, near field communication memory circuit 3404,near field communication transmitter 3406, near field communicationreceiver 3408, power cell module 3414, external interface 3416, data bus3418, and power bus 3420 of the near field communication accessory 3402.In another embodiment, the bottom end portion 3820 of the casing 3600may house the internal interface 3510, TV signal transmitter 3503, TVsignal receiver 3504, service provider transmitter 3507, TV signalprocessor 3506, external interface 3508, security circuit 3518, data bus3514, power bus 3516, and power cell module 3512 of the TV receiveraccessory 3502.

FIG. 38 also illustrates the internal interface connector 3812 thatcouples to the corresponding mobile device interface (e.g, mobile deviceinterface 2460) of the mobile device for the transmission of databetween mobile device and the internal interfaces 2310, 2410, 3310,3410, or 3510 of the particular accessory 2302, 2402, 3302, 3402, or3502 the casing 3600 houses. The internal interface connector 3812 maysnap or lock into place with the mobile device interface to provide asecure physical connection between the accessory 2302, 2402, 3302, 3402,or 3502 and mobile device. The internal interface may also transmitpower from a power cell module 2316, 3414, or 3512 that may be presentin the accessory 2302, 3402, or 3502. In one embodiment the power cellmodules 2316, 3414, and 3512 may be housed within the bottom end portion3820 as disclosed above. However, in another embodiment, the power cellmodules 2316, 3414, and 3512 my be housed within the thickness of theback plane 3802 of the easing 3600. In this case the power cells shouldbe thin so that they can adequately fit within the thickness of the backplane 3802 without significantly increasing the depth/thickness of thecasing 3600.

Referring again to FIG. 36, the casing 3600 may include one or moreopenings 3608, 3612, 3614, 3616 to facilitate access to various featuresof the mobile device 3750. For instance, a first opening 3608 on theback plane 3802 of the casing 3600 may allow an unobstructed view for acamera lens on the back of the mobile device 3750. A second opening 3612may provide access to a screen on/off switch for the mobile device 3750.A third opening 3614 may provide access to an audio jack on the mobiledevice 3750. A fourth opening 3616 on the second side 3806 may provideaccess to a volume control sliding switch.

FIG. 39 illustrates the casing 3600 in an open configuration. The casing3600 may include a top section 3602 and a bottom section 3604 that canbe separated from each other to insert a mobile device within the casing3600, and then be coupled together to secure the mobile device in place.For example, the top section 3602 may include receiving female grooves3902 a and 3902 b that receive male rails 3904 a and 3904 b located onthe bottom section 3604. In this manner, the top section 3602 can becoupled to the bottom section 3604 by pressure fit. For example, atongue section 3906 (see also FIG. 42) may slide on to an engaging tab3908 on the top section 3602 to couple the engaging tab 3908 to areceiving groove 4208 (see FIG. 42) to secure the top section 3602 tothe bottom section 3604.

FIGS. 40 and 41 illustrate a top view and a bottom view, respectively,of the casing 3600. FIG. 40 shows the top side 3810 of the casing 3600,including the first opening 3608, second opening 3612, and third opening3614. FIG. 41 shows the bottom side 3808 of the casing 3600, includingan external interface 4102 (e.g., external interface 2312, of theexternal processing accessory 2302, external interface 3416 of the nearfield communication accessory 3402, or the external interface 3508 ofthe TV receiver accessory 3502), such as a mini-USB connector. Theexternal interface 4102 may serve to recharge a power cell module 2316,3414, and 3512 within the casing 3600, and/or recharge the mobile device3750 via the internal interface connector 3812. Additionally, theexternal interface 4102 may provide a pass-through signaling interfacefor the internal interface connector 3812, thereby allowing the mobiledevice 3750 to communicate to an external source via the externalinterface 4102. A switch 4104 may also be located on the bottom side3808 of the casing 3600. The switch 4104 may power on or off theexternal processing accessory 2302, near field communication accessory3402, or TV receiver accessory 3502 on one setting, and allow the powercell modules within these accessories 2302, 3402, and 3502 to rechargefire mobile device 3750 on another setting.

FIGS. 40 and 41 also illustrate a measurement d that represents themaximum depth of the casing 3600 (also referred herein as the maximumthickness of the casing 3600). In one embodiment, the depth d isdesigned to be as thin as possible so that the overall depth/thicknessof the mobile device 3750 and casing 3600 when joined together is notsubstantially more than the depth/thickness of the mobile device 3750 byitself. In one embodiment, the depth d of the casing 3600 is less thanthe depth/thickness of the mobile device 3750 plus 0.50 inches. Inanother embodiment, the depth d of the casing 3600 is less than thedepth/thickness of the mobile device 3750 plus 0.25 inches. In anotherembodiment, the depth d of the casing 3600 is less than thedepth/thickness of the mobile device 3750 plus 0.125 inches. In anotherembodiment, the depth d of the casing 3600 is less than 1 inch. In yetanother embodiment, the depth d of the casing 3600 is less than 0.75inches. In yet other embodiments, the depth d of the casing 3600 is lessthan 0.5 inches. By having a thin depth/thickness/profile, the casing3600 housing the mobile device 3750 can be conveniently stored, forexample, in the pocket of the user. Casings for mobile deviceaccessories that have a thick depth/profile cannot comfortably be storedin the pocket of a user.

FIG. 42 illustrates a back view of the casing 3600. In one embodiment,the casing 3600 may feature a test button 4202 that when pushed causesplurality of LED lights 4204 to light up. In one embodiment, the LEDlights 4204 may indicate the power or charge level of the power cellmodule 2316, 3414, and 3512. In another embodiment, the LED lights 4204may indicate the signal strength of the TV signals being received fromthe TV service provider by the TV receiver accessory 3502. In anotherembodiment, the LED lights 4204 may indicate the signal strengthdetected by a near field communication device to which the near fieldcommunication accessory 3402 is attempting to communicate with.

Single Piece Bottom Mounted Casing

All of the mobile device accessories disclosed herein, including forexample, the external processing accessory 2302, magnetic card paymentprocessing accessory 2402, smart card payment processing accessory 3302,NFC accessory 3402, and TV receiver accessory 3502 may be housed withina casing 4300 (also referred to as a holster) as shown in FIGS. 43 and44. The casing 4300 is similar to the casing 3600 shown in FIG. 36 butit does not have a top section. Instead, the casing 4300 leaves at leastone side of the mobile device 4450 exposed. The casing 4300 comprises aback plane 4303, a bottom side 4304, a first side 4306, and a secondside 4308. The back plane 4303, the bottom side 4304, the first side4306, and the second side 4308 together form a cavity 4302 in which amobile device may be housed.

FIG. 44 illustrates how a mobile device 4450 may be housed within thecavity 4302 of the casing 4300. FIGS. 43 and 44 also illustrate that thecasing 4300 comprises an end section 4320 that—similar to the endsection 3820—may house within its thickness the hardware components ofthe various accessories 2302, 2402, 3302, 3102, and 3502. As can beappreciated from FIG. 44, the casing 4300 is shaped to closely wraparound the mobile device 4450, and serves as a protective case for themobile device 4450.

The casing 4300 also comprises an internal interface connector 4310 thatcouples to the corresponding mobile device interface (e.g., interface2410) of the mobile device for the transmission of data between themobile device 4450 and the internal interfaces 2310, 2410, 3310, 3410,or 3510 of the particular accessory 2302, 2402, 3302, 3402, or 3502 thecasing 4300 houses. The internal interface connector 4310 may snap orlock into place with the mobile device interface to provide a securephysical connection between the accessory 2302, 2402, 3302, 3402, or3502 and mobile device 4450. The internal interface may also transmitpower from a power cell module 2316, 3414, or 3512 that may be presentin the accessory 2302, 3402, or 3502. In one embodiment the power cellmodules 2316, 3414, and 3512 may be housed within the bottom end portion4320 as disclosed above. However, in another embodiment, the power cellmodules 2316, 3414, and 3512 may be housed within the thickness of theback plane 4303 of the casing 4300. In that case, the power cells shouldbe thin so that they can adequately fit within the thickness of the backplane 4303 without significantly increasing the depth/thickness of thecasing 4300.

FIG. 43 illustrates a measurement d that represents the maximum depth ofthe casing 4300 (also referred herein as the maximum thickness of thecasing 4300). In the one embodiment, the depth d is designed to be asthin as possible so that the overall depth/thickness of the mobiledevice 4450 and casing 4300 when joined together is not substantiallymore than the depth/thickness of the mobile device 4450 by itself. Inone embodiment, the depth d of the casing 4300 is less than thedepth/thickness of the mobile device 4450 plus 0.50 inches. In anotherembodiment, the depth d of the casing 4300 is less than thedepth/thickness of the mobile device 4450 plus 0.25 inches. In anotherembodiment, the depth d of the casing 4300 is less than thedepth/thickness of the mobile device 4450 plus 0.125 inches. In anotherembodiment, the depth d of the casing 4300 is less than 1 inch. In yetanother embodiment, the depth d of the casing 4300 is less than 0.75inches. In yet other embodiments, the depth d of the casing 4300 is lessthan 0.5 inches. By having a thin depth/thickness/profile, the casing4300 housing the mobile device 4450 can be conveniently stored, forexample, in the pocket of the user.

By removing the top section, the mobile accessory may be more compact insize and ergonomic so that it does not significantly increase or changethe size, thickness, and/or shape of the mobile device secured there to.

Bottom Mounted Simple Casing

All of the mobile device accessories disclosed herein, including forexample, the external processing accessory 2302, magnetic card paymentprocessing accessory 2402, smart card payment processing accessory 3302,NFC accessory 3402, and TV receiver accessory 3502 may be housed withina casing 4500 as shown in FIGS. 45 and 46. The casing 4500 is configuredto mount onto an end portion of a mobile device. In the embodiment, thecasing 4500 mounts onto the end portion of the mobile device having amobile device interface, such as, interface 2460 to allow for wire linecommunication between the mobile device and the accessory that may benecessary.

The casing 4500 may include a front side 4502, a back side, a first side4504, a second side 4506, a top side 4508, a bottom side 4512, aninternal interface connector 4510, an external interface 4514, and aswitch 4516. Hardware components of the various accessories 2302. 2402,3302, 3402, and 3502 may be housed within the space formed by the front4502, back, first 4504, second 4506, top 4508 and bottom 4512 sides. Thetop side 4508 of the casing may be shaped to match the end portion ofthe mobile device to which the casing will adhere to. The internalinterface connector 4510 is configured to physically and communicativelycouple to a corresponding mobile device interface of the mobile device.As shown in FIG. 46, once attached to the mobile device interface, theconnector 4510 secures the accessory to the mobile device 4650.

The casing 4500 shown in FIGS. 45 and 46 allows an accessory 2302, 24071302, 3402, or 3502 to be coupled to a mobile device 4650 without theaccessory significantly increasing the weight, thickness and overallsize of the mobile device 4650. The thin depth (also referred to as thethickness) of the casing 4500 and mobile device 4650 combination allowsa user to put the combination (accessory and mobile device) in a smallspace, such as, a pocket. For example, FIG. 45 illustrates a measurementd that represents the maximum depth of the casing 4500. In oneembodiment, the depth d is designed to be as thin as possible so thatthe overall depth/thickness of the mobile device 4650 and casing 4500when joined together is not substantially more than the depth/thicknessof the mobile device 4650 by itself. For example, in one embodiment, thedepth d of the casing 4500 is less than the depth/thickness of themobile device 4650 plus 0.125 inches. In another embodiment, the maximumdepth d of the casing 4500 may be equal or less than the depth/thicknessof the mobile device 1650.

FIG. 45 illustrates the external interface 4514, which in one embodimentmay be a mini-USB connector, that enables communication for the externalinterface 2312 of the external processing accessory 2302, externalinterface 3416 of the near field communication accessory 3402, or theexternal interface 3508 of the TV receiver accessory 3502. The externalinterface 4514 may serve to recharge a power cell module 2316, 3414, and3512 within the casing 4500, and/or recharge the mobile device 4650 viathe internal interface connector 4510. Additionally, the externalinterface 4514 may provide a pass-through signaling interface for theinternal interface connector 4510, thereby allowing the mobile device4650 to communicate to an external source via the external interface4514. A switch 4516 may also be located on the bottom side 4512 of thecasing 4500. The switch 4516 may power on or off the external processingaccessory 2302, near field communication accessory 3402, or TV receiveraccessory 3502 on one setting, and allow the power cell modules withinthese accessories 2302, 3402, and 3502 to recharge the mobile device4650 on another setting.

Thus, the mobile device accessories disclosed herein, including theexternal processing accessory 2302, magnetic strip payment processingaccessory 2402, smart card payment processing accessory 3302, NFCaccessory 3402, TV receiver accessory 3502, a bar code reader mobileaccessory, a finger print reader mobile accessory, and/or a menu viewingand ordering mobile accessory may all be housed within any one of thecasings 3600, 4300, and 4500.

Modular Mobile Accessory Configurations

In various implementations, the mobile accessory may include multipledifferent functionalities and/or capabilities. In order to allow aconsumer to tailor the mobile accessory to his/her needs, the mobileaccessory may be comprised of separate modules or components that can becoupled together to create the physical enclosure of the mobileaccessory.

FIGS. 47 and 48 illustrate various examples of a modular mobileaccessory, where each module may provide a different function. Thus, aconsumer is able to purchase the desired modules and combine them toform the casing enclosure of the mobile accessory.

FIG. 47 illustrates a two-piece modular mobile device accessory scheme4700 that comprises a bottom module 4702 and top module 4704. Eachmodule may incorporate circuits and/or devices that perform differentfunctions, either alone or in combination with other modules. Forinstance, each module may house any one of the mobile accessoriesdescribed above. For example, bottom module 4702 and top module 4704 caneach be a battery pack, an external processing accessory 2302, amagnetic strip payment processing accessory 2402, a smart card paymentprocessing accessory 3302, an NFC accessory 3402, a television signalreceiver and battery pack mobile accessory 3502, a bar code readermobile accessory, a finger print reader mobile accessory, and/or a menuviewing and ordering mobile accessory.

The top module 4704 and bottom module 4702 may join together via contactpoints 4706 to substantially enclose a mobile device contained therein.For example, each contact point 4706 may include a pin that engages acorresponding cavity in the opposite module. In alternativeimplementations, the contact point 4706 may be a magnetic couplerbetween the top and bottom modules 4704 and 4702. Additionally, themodules 4702 and 4704 may include corresponding connectors 4707 and 4709(e.g., male/female connectors) that may electrically couple the twomodules together to allow for electrical communication (e.g., dataand/or control signals) and/or power transfer between the two modules4702 and 4704. For example, the top module 4704 may be a battery packand the bottom module 4702 may be a magnetic strip payment processingaccessory 2402. In such a configuration, the connectors 4707/4709 mayprovide power to the magnetic strip payment processing accessory in thebottom module 4702 from the battery pack in the top module 4704.

FIG. 48 illustrates a functional block diagram of a three-piece modularmobile device accessory scheme 4800 that comprises a bottom module 4802,middle module 4804, and top module 4806. Each module may incorporatecircuits and/or devices that perform different functions, either aloneor in combination with other modules. For instance, each module mayhouse any one of the mobile accessories described above. For example,the bottom module 4802, middle module 4804, and top module 4806 can eachbe a battery pack, a magnetic strip payment processing accessory 2402, asmart card payment processing accessory 3302, a programmable smart cardmobile accessory 3402, a television signal receiver and battery packmobile accessory 3502, a bar code reader mobile accessory, a fingerprint reader mobile accessory, or a menu viewing and ordering mobileaccessory.

The bottom module 4802, middle module 4804, and top module 4806 may besecured together via contact points 4808 to substantially enclose amobile device contained therein. That is, the contact points 4808 mayprovide physical connectors between the modules 4802, 4804, and 4806.

Additionally, the modules 4802, 4804, and 4806 may include correspondingconnectors 4807/4809 and 4811/4813 (e.g., male/female connectors) thatmay electrically couple the modules together to allow for electricalcommunication (e,g., data and/or control signals) and/or power transferbetween the three modules 4802, 4804, 4806. For example, the top module4806 may be a bar code scanner, the middle module 4804 may be fingerprint reader, and the bottom module 4802 may be a credit card reader(e.g., magnetic strip payment processing accessory 2402). In such aconfiguration, the connectors 4807/4809 and 4811/4813 may provide dataand/or control signal communications between the modules 4802, 4804,and/or 4806 and, possibly, with the mobile device to which the mobiledevice accessory 4800 may couple.

The above modular schemes allow multiple mobile accessories to be usedwith one mobile device at the same time. Moreover, rather than having atop section 2504 that merely secures the bottom section 2502 andprotects the mobile device enclosed within, the top, middle, and/orbottom modules of the modular schemes illustrated in FIGS. 47 and 48 mayserve to add a plurality of different combinations of functions orcapabilities to the mobile device since some of the modules may beinterchangeable. For example, a user may select have two modules withbattery pack and a third module with a television receiver.Alternatively, a user may select a first module with a bar code scanner,a second module with a credit card reader, and a third module with aprogrammable smart card device.

Data Management Mobile Accessory

FIG. 49 illustrates a functional block diagram of a data managementsystem 4900 that allows a mobile device 4950 equipped with a datamanagement mobile accessory 4902 to synchronize with and update datastored on a server 4920. For example, the server 4920 may storeinventory/product information for one or more distribution centers orwarehouses. This inventory/product information may comprise, but is notlimited to, type, quantities, images, prices, stock-keeping unit (SKU)identifiers, availability, shipping information, and/or origin ofvarious products. The server 4920 systematically tracks the movement,e.g., in or out, of the products within the one or more distributioncenters.

The server 4920 may also be synchronized with a website 4930. Thewebsite 4930 may display products and product information associatedwith the server 4920 to the anyone accessing the website 4930. Thewebsite 4930 may also be configured to process purchase orders of theproducts, and is capable of updating inventory/product informationstored in the server 4920.

Referring to FIG. 49 and FIG. 50, the data management mobile accessory4902 and mobile device 4950 include hardware and software that allow itto synchronize with and communicate to the server 4920. For example, aunique database management application for a particular data managementsystem 4900 can be designed and created using the SDK 4906 toolsavailable on the data management mobile accessory's memory 4904. Thedatabase management application can be loaded onto and executed on themobile device 4950 through the internal interface 4910. The databasemanagement application allows the user of the mobile device 4950 toconnect to and synchronize with the server 4920 using the datamanagement mobile accessory 4902. For example, the data managementmobile accessory 4902 may include a transmitter and receiver circuit4908 (Tx/Rx Circuit) that allows it to wirelessly connect to the server4920 in order to update any changes that need to be made to theinventory/product information stored within the server 4920, orotherwise access the contents of the server 4920.

In one embodiment, the database management application allows the userof the mobile device 4950 to connect to and synchronize with the server4920 via the website 4930. The mobile device 4950 can connect to thewebsite 4930 using the wireless network service provider associated withthe mobile device 4950. The user of the mobile device 4950 may thenwirelessly update any changes that need to be made to theinventory/product information stored within the server 4920, orotherwise access the contents of the server 4920.

In other embodiments, the data management mobile accessory 4902 mayfurther comprise a processor 4918, a bar code scanner 4912, a magneticstrip/smart card reader interface 4914, and a bus 4916. The bus 4916serves as a line of communication between the internal interface 4910,the processor 4918, the Tx/Rx circuit 4908, the memory 4904, the barcode scanner 4912, and the magnetic strip/smart card reader interface4914. The bar code scanner 4912 allows the user of the data managementmobile accessory 4902 to scan items/products, and update theinventory/product information stored within the server 4920. Forexample, scanning an item may increment the quantity value stored withinthe server 1920 for that particular product. The magnetic strip/smartcard reader interface 4914 enables the user of the data managementmobile accessory 4902 to accept payment card information from a consumerfor a sale transaction according to one of the processes described aboveunder “Payment Processing Mobile Accessories.” If a sale is made thedata management mobile accessory 4902 can update the inventory/productinformation stored within the server 4920 by, for example, decrementingthe quantity value stored within the server 4920 for that particularproduct sold.

Speakers & Microphone

Another feature may provide for one or more speakers to be included aspart of the battery packs or holster (illustrated in FIGS. 1-22). Forinstance a low-profile speaker may be housed within the back plane of abattery pack so that the sound may be emitted from the rear or sides ofthe battery pack. When a mobile device is inserted and coupled to thebattery pack, it couples to an interface that electrically connects thespeaker to the mobile device. The mobile device may send audio or soundsignals to the speaker via an interface with the battery pack. Thisallows a user to listen to audio stored in the mobile device without theneed for headphones.

Similarly, another feature may provide for one or more microphones to beincluded as part of the battery packs (illustrated in FIGS. 1-22). Oneor more microphones may be housed within the battery pack (e.g., backplane) so that they may capture sound from a user. The microphone may beelectrically coupled to an interface that allows sending captured audiosignals to a mobile device that may be coupled to the battery pack.

According to yet another feature, when the mobile device is coupled tothe battery pack 1702, it may cause one or more applications to executeon the processors 1706. These applications may continue to operate orexecute even if the mobile device is removed or decoupled from thebattery pack 1702. For example, the battery pack may continue to collectdata (e.g., monitor medical conditions for a patient to which it iscoupled) and wirelessly transmits the collected data or an alarm to themobile device. This is possible since the processors 1706 be powered bythe power cell 1104 and can be configured to operate whether or not themobile device is coupled to the battery pack.

Integrated Display

In some embodiments of the battery pack 1702, battery pack 1702 may alsoinclude an integrated display or screen. For example, the integrateddisplay may be on the outer surface of the back plane of the batterypack. Alternatively, the display 1710 may slide out from within thehousing of the battery pack. This integrated display 1720 may allowdisplaying additional information or data to a user. The additionaldisplay screen may be electrically coupled to the mobile device (via aninterface) to allow the mobile device to send images or video to theadditional display screen. Alternatively the wireless communicationaccessory's processor could send a battery charge indicator to theintegrated display.

In another example, the rear of the back plane may house a Braille inputand/or output interface that electrically coupled a mobile devicemounted within the holster or battery pack.

In yet another embodiment, the rear of the back plane may provide akeypad that serves as an input to the mobile device.

According to another feature, the battery pack and/or holster mayprovide an external interface (e.g., Bluetooth wireless interface, USBport, infrared port, etc.) that may allow the mobile device mounted inthe battery pack and/or holster to communicate via that externalinterface. Thus the external interface may provide a different wirelessinterface than provided or supported by the internal system of themobile device.

One or more of the features illustrated in FIGS. 1-51 may be rearrangedand or combined into a single component or embodied in severalcomponents. Additional components may also be added without departingfrom the invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other modifications mayoccur to those ordinarily skilled in the art.

The following is claimed:
 1. A wireless communication accessory for amobile device, comprising: a first portion comprising: a back portion,wherein the back portion comprises a terminating edge; a first sidewallconnected to the back portion that will be positioned against a firstside edge of the mobile device; and a second sidewall connected to theback portion at an end opposite the first sidewall that will bepositioned against a second side edge of the mobile device; a secondportion comprising: a third sidewall that will be perpendicular to thefirst sidewall and the second sidewall and positioned against a thirdside edge of the mobile device when the second portion is seated againstthe first portion; and an open side end, opposite of the third sidewallwherein the second portion slides onto the first portion through theopen side end and when the second portion is seated against the firstportion, the mobile device is secured in place by the back portion, thefirst sidewall the second sidewall and the third sidewall, and thescreen of the mobile device will be visible from a direction oppositethe back portion; a processor; an external interface coupled to theprocessor; a wireless communication module coupled to the processor; andan internal interface positioned to connect to a device interface on themobile device and coupled through the processor to the wirelesscommunication module.
 2. The wireless communication accessory of claim1, further comprising a battery cell coupled through the processor tothe internal interface.
 3. The wireless communication accessory of claim2, wherein the battery cell is rechargeable.
 4. The wirelesscommunication accessory of claim 1, wherein the processor is configuredto receive and execute an instruction received from the mobile devicethrough the internal interface.
 5. The wireless communication accessoryof claim 4, wherein the wireless communication accessory is configuredto: transmit a first signal via the external interface when a firstinstruction is sent from the mobile device through the internalinterface; transmit a second signal via the wireless communicationmodule when a second instruction is sent from the mobile device throughthe internal interface; transmit a third signal via the internalinterface to the mobile device when a first data is received at theexternal interface; and transmit a fourth signal via the internalinterface to the mobile device when a second data is received by thewireless communication module.
 6. The wireless communication accessoryof claim 1, wherein the wireless communication module provides adifferent wireless interface than provided or supported by an internalsystem of the mobile device.
 7. The wireless communication accessory ofclaim 1, wherein the wireless communication module is an infrared port,a Bluetooth wireless interface, a nearfield communication (NFC)interface, or a radio frequency identification (RFID) module.
 8. Thewireless communication accessory of claim 1, comprising: a transmittercoupled to the processor, the transmitter configured to transmit a firstdata; and a receiver coupled to the processor, the receiver configuredto receive a second data.
 9. The wireless communication accessory ofclaim 8, wherein the transmitter is a nearfield communication (NFC)transmitter and the receiver is a nearfield communication (NFC)receiver.
 10. The wireless communication accessory of claim 1, furthercomprising a display interface, coupled to the processor, the displayinterface configured to display information to a user of the mobiledevice.
 11. The wireless communication accessory of claim 1, furthercomprising a memory module configured to couple to the mobile devicethrough the internal interface.
 12. The wireless communication accessoryof claim 11, wherein the memory module is removable from the wirelesscommunication accessory.
 13. The wireless communication accessory ofclaim 1, wherein the wireless communication module is removable from thewireless communication accessory.
 14. The wireless communicationaccessory of claim 1, wherein when the second portion is seated againstthe first portion, a first open-polygon-shaped opening for the firstportion merges with a second open-polygon-shaped opening for the secondportion to form a cavity of the wireless communication accessory throughwhich a screen of the mobile device will be visible, the cavity closedon at least four sides.
 15. The wireless communication accessory ofclaim 1, further comprising a transparent screen opposite the backportion, through which a screen of the mobile device will be visible.16. A wireless communication accessory for a mobile device, comprising:a first portion comprising: a back portion, against which a back of ahousing of a mobile device will be placed, wherein the back portioncomprises a terminating edge; a first sidewall, connected to the backportion, that will be positioned against a first side edge of the mobiledevice; a second sidewall, connected to the back portion at an endopposite the first sidewall, that will be positioned against a secondside edge of the mobile device; a third sidewall connected to the backportion at an end opposite of the terminating edge, that will bepositioned against a third side edge of the mobile device; a wirelesscommunication module, enclosed in the first portion; a processor coupledto the wireless communication module; an external interface coupled tothe processor; and an internal interface positioned to connect to adevice interface on the mobile device and coupled through the processorto the wireless communication module; and a second portion comprising: afourth sidewall that will be perpendicular to the first sidewall and thesecond sidewall and positioned against a fourth side edge of the mobiledevice opposite the third side edge when the second portion is seatedagainst the first portion; and an open side end, opposite the fourthsidewall, wherein the second portion slides onto the first portionthrough the open side end and when the second portion is seated againstthe first portion, the mobile device is secured in place by the backportion, the first sidewall, the second sidewall, the third sidewall,and the fourth sidewall, and the screen of the mobile device will bevisible from a direction opposite the back portion.
 17. The wirelesscommunication accessory of claim 16, further comprising a battery cellenclosed in the first portion and coupled through the processor to theinternal interface.
 18. A wireless communication accessory or a mobiledevice, comprising: a first portion comprising: a back portion, againstwhich a back of a housing of a mobile device will be placed, wherein theback portion comprises a terminating edge; a first sidewall connected tothe back portion that will be positioned against a first side edge ofthe mobile device; and a second sidewall connected to the back portionat an end opposite the first sidewall that will be positioned against asecond side edge of the mobile device; a second portion comprising: athird sidewall that will be perpendicular to the first sidewall and thesecond sidewall and positioned against a third side edge of the mobiledevice when the second portion is seated against the first portion; anopen side end, opposite of the third sidewall, wherein the secondportion slides onto the first portion through the open side end and whenthe second portion is seated against the first portion, the mobiledevice is secured in place by the back portion, the first sidewall, thesecond sidewall, and the third sidewall, and the screen of the mobiledevice will be visible from a direction opposite the back portion; aprocessor; a wireless communication module coupled to the processor; aninternal interface positioned to connect to a device interface on themobile device and coupled through the processor to the wirelesscommunication module; and an external interface coupled to theprocessor.
 19. The wireless communication accessory of claim 18, whereinthe first portion and second portion are communicatively coupled whenthe second portion is seated against the first portion.
 20. The wirelesscommunication accessory of claim 18, further comprising a battery cellenclosed in the first portion and communicatively coupled through theprocessor to the internal interface when the second portion is seatedagainst the first portion.